System for data routing in networks

ABSTRACT

Systems, methods, and devices for routing data in a network are described. A user device may send a request for video data that has been captured by a premises device. A computing device at the premises may receive the request and determine a capability of the user device. Based on the capability of the user device, the computing device may select a protocol from a plurality of protocols with which the video data is to be transmitted to the user device. Based on determining that the video data cannot be transmitted via the computing device, the video data may be transmitted from the premises device to the user device via the determined protocol.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of, and claims priorityto, U.S. patent application Ser. No. 15/673,185, filed Aug. 9, 2017, nowU.S. Pat. No. 10,999,254, issued May 4, 2021, which is a continuationapplication of, and claims priority to, U.S. patent application Ser. No.13/531,757, filed Jun. 25, 2012, now abandoned.

U.S. patent application Ser. No. 13/531,757 is:

a continuation application of U.S. patent application Ser. No.12/198,023, filed Aug. 25, 2008, now U.S. Pat. No. 8,209,400, issuedJun. 26, 2012;

a continuation in part application of U.S. patent application Ser. No.11/084,232, filed Mar. 16, 2005, now U.S. Pat. No. 8,335,842, issuedDec. 18, 2012;

a continuation in part application of U.S. patent application Ser. No.11/761,745, filed Jun. 12, 2007, now U.S. Pat. No. 8,635,350, issuedJan. 21, 2014;

a continuation in part application of U.S. patent application Ser. No.12/189,757, filed Aug. 11, 2008, now U.S. Pat. No. 8,473,619, issuedJun. 25, 2013;

a continuation in part application of U.S. patent application Ser. No.12/197,931, filed Aug. 25, 2008, now U.S. Pat. No. 9,172,553, issuedOct. 27, 2015;

a continuation in part application of U.S. patent application Ser. No.12/269,735, filed Nov. 12, 2008, now U.S. Pat. No. 8,996,665, issuedMar. 31, 2015; and

a continuation in part application of U.S. patent application Ser. No.12/637,671, filed Dec. 14, 2009, now U.S. Pat. No. 8,478,871, issuedJul. 2, 2013.

U.S. patent application Ser. No. 12/198,023 claims priority to:

U.S. Provisional Application No. 60/968,005, filed Aug. 24, 2007;

U.S. Provisional Application No. 60/957,997, filed Aug. 24, 2007;

U.S. Provisional Application No. 60/987,359, filed Nov. 12, 2007;

U.S. Provisional Application No. 60/987,366, filed Nov. 12, 2007;

U.S. Provisional Application No. 61/019,162, filed Jan. 4, 2008;

U.S. Provisional Application No. 61/019,167, filed Jan. 4, 2008;

U.S. Provisional Application No. 61/023,496, filed Jan. 25, 2008;

U.S. Provisional Application No. 61/023,493, filed Jan. 25, 2008;

U.S. Provisional Application No. 61/023,489, filed Jan. 25, 2008; and

U.S. Provisional Application No. 61/087,967, filed Aug. 11, 2008.

Each of the foregoing U.S. Patent Applications and U.S. ProvisionalApplications are incorporated by reference herein in their entireties.

BACKGROUND

The field of home and small business security is dominated by technologysuppliers who build comprehensive ‘closed’ security systems, where theindividual components (sensors, security panels, keypads) operate solelywithin the confines of a single vendor solution. For example, a wirelessmotion sensor from vendor A cannot be used with a security panel fromvendor B. Each vendor typically has developed sophisticated proprietarywireless technologies to enable the installation and management ofwireless sensors, with little or no ability for the wireless devices tooperate separate from the vendor's homogeneous system. Furthermore,these traditional systems are extremely limited in their ability tointerface either to a local or wide area standards-based network (suchas an Internet Protocol (IP) network); most installed systems supportonly a low-bandwidth, intermittent connection utilizing phone lines orcellular (RF) backup systems. Wireless security technology fromproviders such as GE Security, Honeywell, and DSC/Tyco are well known inthe art, and are examples of this proprietary approach to securitysystems for home and business.

Furthermore, with the proliferation of the internet, ethernet and WiFilocal area networks (LANs) and advanced wide area networks (WANs) thatoffer high bandwidth, low latency connections (broadband), as well asmore advanced wireless WAN data networks (e.g. GPRS or CDMA 1×RTT) thereincreasingly exists the networking capability to extend thesetraditional security systems to offer enhanced functionality. Inaddition, the proliferation of broadband access has driven acorresponding increase in home and small business networkingtechnologies and devices. It is desirable to extend traditional securitysystems to encompass enhanced functionality such as the ability tocontrol and manage security systems from the world wide web, cellulartelephones, or advanced function internet-based devices. Other desiredfunctionality includes an open systems approach to interface homesecurity systems to home and small business networks.

Due to the proprietary approach described above, the traditional vendorsare the only ones capable of taking advantage of these new networkfunctions. To date, even though the vast majority of home and businesscustomers have broadband network access in their premises, most securitysystems do not offer the advanced capabilities associated with highspeed, low-latency LANs and WANs. This is primarily because theproprietary vendors have not been able to deliver such technologyefficiently or effectively. Solution providers attempting to addressthis need are becoming known in the art, including three categories ofvendors: traditional proprietary hardware providers such as Honeywelland GE Security; third party hard-wired module providers such asAlarm.com, NextAlarm, and uControl; and new proprietary systemsproviders such as InGrid.

A disadvantage of the prior art technologies of the traditionalproprietary hardware providers arises due to the continued proprietaryapproach of these vendors. As they develop technology in this area itonce again operates only with the hardware from that specific vendor,ignoring the need for a heterogeneous, cross-vendor solution. Yetanother disadvantage of the prior art technologies of the traditionalproprietary hardware providers arises due to the lack of experience andcapability of these companies in creating open internet and web basedsolutions, and consumer friendly interfaces.

A disadvantage of the prior art technologies of the third partyhard-wired module providers arises due to the installation andoperational complexities and functional limitations associated withhardwiring a new component into existing security systems. Moreover, adisadvantage of the prior art technologies of the new proprietarysystems providers arises due to the need to discard all priortechnologies, and implement an entirely new form of security system toaccess the new functionalities associated with broadband and wirelessdata networks. There remains, therefore, a need for systems, devices,and methods that easily interface to and control the existingproprietary security technologies utilizing a variety of wirelesstechnologies.

INCORPORATION BY REFERENCE

Each patent, patent application, and/or publication mentioned in thisspecification is herein incorporated by reference in its entirety to thesame extent as if each individual patent, patent application, and/orpublication was specifically and individually indicated to beincorporated by reference.

SUMMARY

Systems, methods, and devices are described herein for data routing innetworks. A method may comprise a computing device receiving a requestfrom a user device for video data from a premises device. The premisesdevice may be in communication with the computing device. The computingdevice and the premises device may be located at a first location andthe user device may be located at a different second location. Thecomputing device may determine a capability of the user device. Thecomputing device may determine a protocol from a plurality of protocolsbased on the capability of the user device. The video data may betransmitted, based on determining that the video data cannot betransmitted via the computing device, from the premises device to theuser device via the determined protocol.

A method may comprise a server receiving a request for video data from apremises device that is in communication with a computing device. Therequest may be received from a user device. The computing device and thepremises device may be located at a first location. The server may belocated at a second location different from the first location. The userdevice may be located at a third location different from the firstlocation and the second location. The server may determine a capabilityof the user device. The server may determine a protocol from a pluralityof protocols based on the capability of the user device. The video datamay be transmitted, based on determining that the video data cannot betransmitted via the computing device, from the premises device to theuser device via the determined protocol.

A system may comprise a premises device located at a first location andconfigured to capture video data. The system may further comprise acomputing device located at the first location and configured tocommunicate with the premises device. The system may further comprise aserver configured to communicate with the computing device and locatedat a second location different from the first location. At least one ofthe server or the computing device may be configured to receive, from auser device, a request for the video data captured by the premisesdevice and determine a capability of the user device. The user devicemay be located at a third location different from the first location andthe second location. At least one of the server or the computing devicemay be configured to determine a protocol from a plurality of protocolsbased on the capability of the user device. At least one of the serveror the computing device may be configured to cause, based on determiningthat the video data cannot be transmitted via the computing device, thevideo data to be transmitted from the premises device to the user devicevia the determined protocol.

A device may comprise one or more processors and memory storinginstructions. When executed by the one or more processors, theinstructions may cause the device to receive, from a user device, arequest for video data from a premises device located at a firstlocation. The device may be located at the first location and configuredto communicate with the premises device. The user device may be locatedat a second location different from the first location. When executed bythe one or more processors, the instructions may further cause thedevice to determine a capability of the user device and determine, basedon the capability of the user device, a protocol from a plurality ofprotocols. When executed by the one or more processors, the instructionsmay further cause the device to cause, based on determining that thevideo data cannot be transmitted via the device, the video data to betransmitted from the premises device to the user device via thedetermined protocol.

A device may comprise one or more processors and memory storinginstructions. When executed by the one or more processors, theinstructions may cause the device to receive, from a user device, arequest for video data from a premises device configured to communicatewith a computing device. The computing device and the premises devicemay be located at a first location. The device may be located at asecond location different from the first location. The user device maybe located at a third location different from the first location and thesecond location. When executed by the one or more processors, theinstructions may further cause the device to determine a capability ofthe user device and determine, based on the capability of the userdevice, a protocol from a plurality of protocol. When executed by theone or more processors, the instructions may further cause the device tocause, based on determining that the video data cannot be transmittedvia the computing device, the video data to be transmitted from thepremises device to the user device via the determined protocol.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of the integrated security system, under anembodiment.

FIG. 2 is a block diagram of components of the integrated securitysystem, under an embodiment.

FIG. 3 is a block diagram of the gateway software or applications, underan embodiment.

FIG. 4 is a block diagram of the gateway components, under anembodiment.

FIG. 5 is a block diagram of IP device integration with a premisesnetwork, under an embodiment.

FIG. 6 is a block diagram of IP device integration with a premisesnetwork, under an alternative embodiment.

FIG. 7 is a block diagram of a touchscreen, under an embodiment.

FIG. 8 is an example screenshot of a networked security touchscreen,under an embodiment.

FIG. 9 is a block diagram of network or premises device integration witha premises network, under an embodiment.

FIG. 10 is a block diagram of network or premises device integrationwith a premises network, under an alternative embodiment.

FIG. 11 is a flow diagram for installation of an IP device into aprivate network environment, under an embodiment.

FIG. 12 is a block diagram showing communications among IP devices ofthe private network environment, under an embodiment.

FIG. 13 is a general flow diagram for IP video control, under anembodiment.

FIG. 14 is a flow diagram of a method of integrating an external controland management application system with an existing security system,under an embodiment.

FIG. 15 is a block diagram of an integrated security system wirelesslyinterfacing to proprietary security systems, under an embodiment.

FIG. 16 is a flow diagram for wirelessly ‘learning’ the gateway into anexisting security system and discovering extant sensors, under anembodiment.

DETAILED DESCRIPTION

An integrated security system is described that integrates broadband andmobile access and control with conventional security systems andpremises devices to provide a tri-mode security network (broadband,cellular/GSM, POTS access) that enables users to remotely stay connectedto their premises. The integrated security system, while deliveringremote premises monitoring and control functionality to conventionalmonitored premises protection, complements existing premises protectionequipment. The integrated security system integrates into the premisesnetwork and couples wirelessly with the conventional security panel,enabling broadband access to premises security systems. Automationdevices (cameras, lamp modules, thermostats, etc.) can be added,enabling users to remotely see live video and/or pictures and controlhome devices via their personal web portal or webpage, mobile phone,and/or other remote client device. Users can also receive notificationsvia email or text message when happenings occur, or do not occur, intheir home.

Although the detailed description herein contains many specifics for thepurposes of illustration, anyone of ordinary skill in the art willappreciate that many variations and alterations to the following detailsare within the scope of the embodiments described herein. Thus, thefollowing illustrative embodiments are set forth without any loss ofgenerality to, and without imposing limitations upon, the claimedinvention.

In accordance with the embodiments described herein, a wireless system(e.g., radio frequency (RF)) is provided that enables a securityprovider or consumer to extend the capabilities of an existingRF-capable security system or a non-RF-capable security system that hasbeen upgraded to support RF capabilities. The system includes anRF-capable Gateway device (physically located within RF range of theRF-capable security system) and associated software operating on theGateway device. The system also includes a web server, applicationserver, and remote database providing a persistent store for informationrelated to the system.

The security systems of an embodiment, referred to herein as theiControl security system or integrated security system, extend the valueof traditional home security by adding broadband access and theadvantages of remote home monitoring and home control through theformation of a security network including components of the integratedsecurity system integrated with a conventional premises security systemand a premises local area network (LAN). With the integrated securitysystem, conventional home security sensors, cameras, touchscreenkeypads, lighting controls, and/or Internet Protocol (IP) devices in thehome (or business) become connected devices that are accessible anywherein the world from a web browser, mobile phone or through content-enabledtouchscreens. The integrated security system experience allows securityoperators to both extend the value proposition of their monitoredsecurity systems and reach new consumers that include broadband usersinterested in staying connected to their family, home and property whenthey are away from home.

The integrated security system of an embodiment includes securityservers (also referred to herein as iConnect servers or security networkservers) and an iHub gateway (also referred to herein as the gateway,the iHub, or the iHub client) that couples or integrates into a homenetwork (e.g., LAN) and communicates directly with the home securitypanel, in both wired and wireless installations. The security system ofan embodiment automatically discovers the security system components(e.g., sensors, etc.) belonging to the security system and connected toa control panel of the security system and provides consumers with fulltwo-way access via web and mobile portals. The gateway supports variouswireless protocols and can interconnect with a wide range of controlpanels offered by security system providers. Service providers and userscan then extend the system's capabilities with the additional IPcameras, lighting modules or security devices such as interactivetouchscreen keypads. The integrated security system adds an enhancedvalue to these security systems by enabling consumers to stay connectedthrough email and SMS alerts, photo push, event-based video capture andrule-based monitoring and notifications. This solution extends the reachof home security to households with broadband access.

The integrated security system builds upon the foundation afforded bytraditional security systems by layering broadband and mobile access, IPcameras, interactive touchscreens, and an open approach to homeautomation on top of traditional security system configurations. Theintegrated security system is easily installed and managed by thesecurity operator, and simplifies the traditional security installationprocess, as described below.

The integrated security system provides an open systems solution to thehome security market. As such, the foundation of the integrated securitysystem customer premises equipment (CPE) approach has been to abstractdevices, and allows applications to manipulate and manage multipledevices from any vendor. The integrated security system DeviceConnecttechnology that enables this capability supports protocols, devices, andpanels from GE Security and Honeywell, as well as consumer devices usingZ-Wave, IP cameras (e.g., Ethernet, wifi, and Homeplug), and IPtouchscreens. The DeviceConnect is a device abstraction layer thatenables any device or protocol layer to interoperate with integratedsecurity system components. This architecture enables the addition ofnew devices supporting any of these interfaces, as well as add entirelynew protocols.

The benefit of DeviceConnect is that it provides supplier flexibility.The same consistent touchscreen, web, and mobile user experience operateunchanged on whatever security equipment selected by a security systemprovider, with the system provider's choice of IP cameras, backend datacenter and central station software.

The integrated security system provides a complete system thatintegrates or layers on top of a conventional host security systemavailable from a security system provider. The security system providertherefore can select different components or configurations to offer(e.g., CDMA, GPRS, no cellular, etc.) as well as have iControl modifythe integrated security system configuration for the system provider'sspecific needs (e.g., change the functionality of the web or mobileportal, add a GE or Honeywell-compatible TouchScreen, etc.).

The integrated security system integrates with the security systemprovider infrastructure for central station reporting directly viaBroadband and GPRS alarm transmissions. Traditional dial-up reporting issupported via the standard panel connectivity. Additionally, theintegrated security system provides interfaces for advancedfunctionality to the CMS, including enhanced alarm events, systeminstallation optimizations, system test verification, videoverification, 2-way voice over IP and GSM.

The integrated security system is an IP centric system that includesbroadband connectivity so that the gateway augments the existingsecurity system with broadband and GPRS connectivity. If broadband isdown or unavailable GPRS may be used, for example. The integratedsecurity system supports GPRS connectivity using an optional wirelesspackage that includes a GPRS modem in the gateway. The integratedsecurity system treats the GPRS connection as a higher cost thoughflexible option for data transfers. In an embodiment the GPRS connectionis only used to route alarm events (e.g., for cost), however the gatewaycan be configured (e.g., through the iConnect server interface) to actas a primary channel and pass any or all events over GPRS. Consequently,the integrated security system does not interfere with the current plainold telephone service (POTS) security panel interface. Alarm events canstill be routed through POTS; however the gateway also allows suchevents to be routed through a broadband or GPRS connection as well. Theintegrated security system provides a web application interface to theCSR tool suite as well as XML web services interfaces for programmaticintegration between the security system provider's existing call centerproducts. The integrated security system includes, for example, APIsthat allow the security system provider to integrate components of theintegrated security system into a custom call center interface. The APIsinclude XML web service APIs for integration of existing security systemprovider call center applications with the integrated security systemservice. All functionality available in the CSR Web application isprovided with these API sets. The Java and XML-based APIs of theintegrated security system support provisioning, billing, systemadministration, CSR, central station, portal user interfaces, andcontent management functions, to name a few. The integrated securitysystem can provide a customized interface to the security systemprovider's billing system, or alternatively can provide security systemdevelopers with APIs and support in the integration effort.

The integrated security system provides or includes business componentinterfaces for provisioning, administration, and customer care to name afew. Standard templates and examples are provided with a definedcustomer professional services engagement to help integrate OSS/BSSsystems of a Service Provider with the integrated security system.

The integrated security system components support and allow for theintegration of customer account creation and deletion with a securitysystem. The iConnect APIs provides access to the provisioning andaccount management system in iConnect and provide full support foraccount creation, provisioning, and deletion. Depending on therequirements of the security system provider, the iConnect APIs can beused to completely customize any aspect of the integrated securitysystem backend operational system.

The integrated security system includes a gateway that supports thefollowing standards-based interfaces, to name a few: Ethernet IPcommunications via Ethernet ports on the gateway, and standardXML/TCP/IP protocols and ports are employed over secured secure socketlayer (SSL) sessions; USB 2.0 via ports on the gateway; 802.11b/g/n IPcommunications; GSM/GPRS RF WAN communications; CDMA 1×RTT RF WANcommunications (optional, can also support EVDO and 3G technologies).

The gateway supports the following proprietary interfaces, to name afew: interfaces including Dialog RF network (319.5 MHz) and RS485Superbus 2000 wired interface; RF mesh network (908 MHz); and interfacesincluding RF network (345 MHz) and RS485/RS232bus wired interfaces.

Regarding security for the IP communications (e.g., authentication,authorization, encryption, anti-spoofing, etc.), the integrated securitysystem uses SSL to encrypt all IP traffic, using server andclient-certificates for authentication, as well as authentication in thedata sent over the SSL-encrypted channel. For encryption, integratedsecurity system issues public/private key pairs at the time/place ofmanufacture, and certificates are not stored in any online storage in anembodiment.

The integrated security system does not need any special rules at thecustomer premises and/or at the security system provider central stationbecause the integrated security system makes outgoing connections usingTransmission Control Protocol (TCP) over the standard Hypertext TransferProtocol (HTTP) and Hyptertext Transfer Protocol over Secure SocketLayer (HTTPS) ports. Provided outbound TCP connections are allowed thenno special requirements on the firewalls are necessary.

FIG. 1 is a block diagram of the integrated security system 100, underan embodiment. The integrated security system 100 of an embodimentincludes the gateway 102 and the security servers 104 coupled to theconventional home security system 110. At a customer's home or business,the gateway 102 connects and manages the diverse variety of homesecurity and self-monitoring devices. The gateway 102 communicates withthe iConnect Servers 104 located in the service provider's data center106 (or hosted in integrated security system data center), with thecommunication taking place via a communication network 108 or othernetwork (e.g., cellular network, internet, etc.). These servers 104manage the system integrations necessary to deliver the integratedsystem service described herein. The combination of the gateway 102 andthe iConnect servers 104 enable a wide variety of remote clients 120(e.g., PCs, mobile phones and PDAs) allowing users to remotely stay intouch with their home, business and family. In addition, the technologyallows home security and self-monitoring information, as well asrelevant third party content such as traffic and weather, to bepresented in intuitive ways within the home, such as on advancedtouchscreen keypads.

The integrated security system service (also referred to as iControlservice) can be managed by a service provider via browser-basedMaintenance and Service Management applications that are provided withthe iConnect Servers. Or, if desired, the service can be more tightlyintegrated with existing OS SB SS and service delivery systems via theiConnect web services-based XML APIs.

The integrated security system service can also coordinate the sendingof alarms to the home security Central Monitoring Station (CMS) 199.Alarms are passed to the CMS 199 using standard protocols such asContact ID or SIA and can be generated from the home security panellocation as well as by iConnect server 104 conditions (such as lack ofcommunications with the integrated security system). In addition, thelink between the security servers 104 and CMS 199 provides tighterintegration between home security and self-monitoring devices and thegateway 102. Such integration enables advanced security capabilitiessuch as the ability for CMS personnel to view photos taken at the time aburglary alarm was triggered. For maximum security, the gateway 102 andiConnect servers 104 support the use of a mobile network (both GPRS andCDMA options are available) as a backup to the primary broadbandconnection.

The integrated security system service is delivered by hosted serversrunning software components that communicate with a variety of clienttypes while interacting with other systems. FIG. 2 is a block diagram ofcomponents of the integrated security system 100, under an embodiment.Following is a more detailed description of the components.

The iConnect servers 104 support a diverse collection of clients 120ranging from mobile devices, to PCs, to in-home security devices, to aservice provider's internal systems. Most clients 120 are used byend-users, but there are also a number of clients 120 that are used tooperate the service.

Clients 120 used by end-users of the integrated security system 100include, but are not limited to, the following:

Clients based on gateway client applications 202 (e.g., aprocessor-based device running the gateway technology that manages homesecurity and automation devices).

A web browser 204 accessing a Web Portal application, performingend-user configuration and customization of the integrated securitysystem service as well as monitoring of in-home device status, viewingphotos and video, etc. Device and user management can also be performedby this portal application.

A mobile device 206 (e.g., PDA, mobile phone, etc.) accessing theintegrated security system Mobile Portal. This type of client is used byend-users to view system status and perform operations on devices (e.g.,turning on a lamp, arming a security panel, etc.) rather than for systemconfiguration tasks such as adding a new device or user.

PC or browser-based “widget” containers 208 that present integratedsecurity system service content, as well as other third-party content,in simple, targeted ways (e.g. a widget that resides on a PC desktop andshows live video from a single in-home camera). “Widget” as used hereinmeans applications or programs in the system.

Touchscreen home security keypads 208 and advanced in-home devices thatpresent a variety of content widgets via an intuitive touchscreen userinterface.

Notification recipients 210 (e.g., cell phones that receive SMS-basednotifications when certain events occur (or don't occur), email clientsthat receive an email message with similar information, etc.).

Custom-built clients (not shown) that access the iConnect web servicesXML API to interact with users' home security and self-monitoringinformation in new and unique ways. Such clients could include new typesof mobile devices, or complex applications where integrated securitysystem content is integrated into a broader set of application features.

In addition to the end-user clients, the iConnect servers 104 support PCbrowser-based Service Management clients that manage the ongoingoperation of the overall service. These clients run applications thathandle tasks such as provisioning, service monitoring, customer supportand reporting.

There are numerous types of server components of the iConnect servers104 of an embodiment including, but not limited to, the following:Business Components which manage information about all of the homesecurity and self-monitoring devices; End-User Application Componentswhich display that information for users and access the BusinessComponents via published XML APIs; and Service Management ApplicationComponents which enable operators to administer the service (thesecomponents also access the Business Components via the XML APIs, andalso via published SNMP MIBs).

The server components provide access to, and management of, the objectsassociated with an integrated security system installation. Thetop-level object is the “network.” It is a location where a gateway 102is located, and is also commonly referred to as a site or premises; thepremises can include any type of structure (e.g., home, office,warehouse, etc.) at which an gateway 102 is located. Users can onlyaccess the networks to which they have been granted permission. Within anetwork, every object monitored by the gateway 102 is called a device.Devices include the sensors, cameras, home security panels andautomation devices, as well as the controller or processor-based devicerunning the gateway applications.

Various types of interactions are possible between the objects in asystem. Automations define actions that occur as a result of a change instate of a device. For example, take a picture with the front entrycamera when the front door sensor changes to “open”. Notifications aremessages sent to users to indicate that something has occurred, such asthe front door going to “open” state, or has not occurred (referred toas an iWatch notification). Schedules define changes in device statesthat are to take place at predefined days and times. For example, setthe security panel to “Armed” mode every weeknight at 11:00 pm.

The iConnect Business Components are responsible for orchestrating allof the low-level service management activities for the integratedsecurity system service. They define all of the users and devicesassociated with a network (site), analyze how the devices interact, andtrigger associated actions (such as sending notifications to users). Allchanges in device states are monitored and logged. The BusinessComponents also manage all interactions with external systems asrequired, including sending alarms and other related self-monitoringdata to the home security Central Monitoring System (CMS) 199. TheBusiness Components are implemented as portable Java J2EE Servlets, butare not so limited.

The following iConnect Business Components manage the main elements ofthe integrated security system service, but the embodiment is not solimited:

A Registry Manager 220 defines and manages users and networks. Thiscomponent is responsible for the creation, modification and terminationof users and networks. It is also where a user's access to networks isdefined.

A Network Manager 222 defines and manages security and self-monitoringdevices that are deployed on a network (site). This component handlesthe creation, modification, deletion and configuration of the devices,as well as the creation of automations, schedules and notification rulesassociated with those devices.

A Data Manager 224 manages access to current and logged state data foran existing network and its devices. This component specifically doesnot provide any access to network management capabilities, such asadding new devices to a network, which are handled exclusively by theNetwork Manager 222.

To achieve optimal performance for all types of queries, data forcurrent device states is stored separately from historical state data(a.k.a. “logs”) in the database. A Log Data Manager 226 performs ongoingtransfers of current device state data to the historical data logtables.

Additional iConnect Business Components handle direct communicationswith certain clients and other systems, for example:

An iHub Manager 228 directly manages all communications with gatewayclients, including receiving information about device state changes,changing the configuration of devices, and pushing new versions of thegateway client to the hardware it is running on.

A Notification Manager 230 is responsible for sending all notificationsto clients via SMS (mobile phone messages), email (via a relay serverlike an SMTP email server), etc.

An Alarm and CMS Manager 232 sends critical server-generated alarmevents to the home security Central Monitoring Station (CMS) and managesall other communications of integrated security system service data toand from the CMS.

The Element Management System (EMS) 234 is an iControl BusinessComponent that manages all activities associated with serviceinstallation, scaling and monitoring, and filters and packages serviceoperations data for use by service management applications. The SNMPMIBs published by the EMS can also be incorporated into any third partymonitoring system if desired.

The iConnect Business Components store information about the objectsthat they manage in the iControl Service Database 240 and in theiControl Content Store 242. The iControl Content Store is used to storemedia objects like video, photos and widget content, while the ServiceDatabase stores information about users, networks, and devices. Databaseinteraction is performed via a JDBC interface. For security purposes,the Business Components manage all data storage and retrieval.

The iControl Business Components provide web services-based APIs thatapplication components use to access the Business Components'capabilities. Functions of application components include presentingintegrated security system service data to end-users, performingadministrative duties, and integrating with external systems andback-office applications.

The primary published APIs for the iConnect Business Components include,but are not limited to, the following:

A Registry Manager API 252 provides access to the Registry ManagerBusiness Component's functionality, allowing management of networks andusers.

A Network Manager API 254 provides access to the Network ManagerBusiness Component's functionality, allowing management of devices on anetwork.

A Data Manager API 256 provides access to the Data Manager BusinessComponent's functionality, such as setting and retrieving (current andhistorical) data about device states.

A Provisioning API 258 provides a simple way to create new networks andconfigure initial default properties.

Each API of an embodiment includes two modes of access: Java API or XMLAPI. The XML APIs are published as web services so that they can beeasily accessed by applications or servers over a network. The Java APIsare a programmer-friendly wrapper for the XML APIs. Applicationcomponents and integrations written in Java should generally use theJava APIs rather than the XML APIs directly.

The iConnect Business Components also have an XML-based interface 260for quickly adding support for new devices to the integrated securitysystem. This interface 260, referred to as DeviceConnect, is a flexible,standards-based mechanism for defining the properties of new devices andhow they can be managed. Although the format is flexible enough to allowthe addition of any type of future device, pre-defined XML profiles arecurrently available for adding common types of devices such as sensors(SensorConnect), home security panels (PanelConnect) and IP cameras(CameraConnect).

The iConnect End-User Application Components deliver the user interfacesthat run on the different types of clients supported by the integratedsecurity system service. The components are written in portable JavaJ2EE technology (e.g., as Java Servlets, as JavaServer Pages (JSPs),etc.) and they all interact with the iControl Business Components viathe published APIs.

The following End-User Application Components generate CSS-basedHTML/JavaScript that is displayed on the target client. Theseapplications can be dynamically branded with partner-specific logos andURL links (such as Customer Support, etc.). The End-User ApplicationComponents of an embodiment include, but are not limited to, thefollowing:

An iControl Activation Application 270 that delivers the firstapplication that a user sees when they set up the integrated securitysystem service. This wizard-based web browser application securelyassociates a new user with a purchased gateway and the other devicesincluded with it as a kit (if any). It primarily uses functionalitypublished by the Provisioning API.

An iControl Web Portal Application 272 runs on PC browsers and deliversthe web-based interface to the integrated security system service. Thisapplication allows users to manage their networks (e.g. add devices andcreate automations) as well as to view/change device states, and managepictures and videos. Because of the wide scope of capabilities of thisapplication, it uses three different Business Component APIs thatinclude the Registry Manager API, Network Manager API, and Data ManagerAPI, but the embodiment is not so limited.

An iControl Mobile Portal 274 is a small-footprint web-based interfacethat runs on mobile phones and PDAs. This interface is optimized forremote viewing of device states and pictures/videos rather than networkmanagement. As such, its interaction with the Business Components isprimarily via the Data Manager API.

Custom portals and targeted client applications can be provided thatleverage the same Business Component APIs used by the aboveapplications.

A Content Manager Application Component 276 delivers content to avariety of clients. It sends multimedia-rich user interface componentsto widget container clients (both PC and browser-based), as well as toadvanced touchscreen keypad clients. In addition to providing contentdirectly to end-user devices, the Content Manager 276 provideswidget-based user interface components to satisfy requests from otherApplication Components such as the iControl Web 272 and Mobile 274portals.

A number of Application Components are responsible for overallmanagement of the service. These pre-defined applications, referred toas Service Management Application Components, are configured to offeroff-the-shelf solutions for production management of the integratedsecurity system service including provisioning, overall servicemonitoring, customer support, and reporting, for example. The ServiceManagement Application Components of an embodiment include, but are notlimited to, the following:

A Service Management Application 280 allows service administrators toperform activities associated with service installation, scaling andmonitoring/alerting. This application interacts heavily with the ElementManagement System (EMS) Business Component to execute its functionality,and also retrieves its monitoring data from that component via protocolssuch as SNMP MIBs.

A Kitting Application 282 is used by employees performing serviceprovisioning tasks. This application allows home security andself-monitoring devices to be associated with gateways during thewarehouse kitting process.

A CSR Application and Report Generator 284 is used by personnelsupporting the integrated security system service, such as CSRsresolving end-user issues and employees enquiring about overall serviceusage. Pushes of new gateway firmware to deployed gateways is alsomanaged by this application.

The iConnect servers 104 also support custom-built integrations with aservice provider's existing OSS/BSS, CSR and service delivery systems290. Such systems can access the iConnect web services XML API totransfer data to and from the iConnect servers 104. These types ofintegrations can complement or replace the PC browser-based ServiceManagement applications, depending on service provider needs.

As described above, the integrated security system of an embodimentincludes a gateway, or iHub. The gateway of an embodiment includes adevice that is deployed in the home or business and couples or connectsthe various third-party cameras, home security panels, sensors anddevices to the iConnect server over a WAN connection as described indetail herein. The gateway couples to the home network and communicatesdirectly with the home security panel in both wired and wireless sensorinstallations. The gateway is configured to be low-cost, reliable andthin so that it complements the integrated security system network-basedarchitecture.

The gateway supports various wireless protocols and can interconnectwith a wide range of home security control panels. Service providers andusers can then extend the system's capabilities by adding IP cameras,lighting modules and additional security devices. The gateway isconfigurable to be integrated into many consumer appliances, includingset-top boxes, routers and security panels. The small and efficientfootprint of the gateway enables this portability and versatility,thereby simplifying and reducing the overall cost of the deployment.

FIG. 3 is a block diagram of the gateway 102 including gateway softwareor applications, under an embodiment. The gateway software architectureis relatively thin and efficient, thereby simplifying its integrationinto other consumer appliances such as set-top boxes, routers, touchscreens and security panels. The software architecture also provides ahigh degree of security against unauthorized access. This sectiondescribes the various key components of the gateway softwarearchitecture.

The gateway application layer 302 is the main program that orchestratesthe operations performed by the gateway. The Security Engine 304provides robust protection against intentional and unintentionalintrusion into the integrated security system network from the outsideworld (both from inside the premises as well as from the WAN). TheSecurity Engine 304 of an embodiment comprises one or more sub-modulesor components that perform functions including, but not limited to, thefollowing:

Encryption including 128-bit SSL encryption for gateway and iConnectserver communication to protect user data privacy and provide securecommunication.

Bi-directional authentication between the gateway and iConnect server inorder to prevent unauthorized spoofing and attacks. Data sent from theiConnect server to the gateway application (or vice versa) is digitallysigned as an additional layer of security. Digital signing provides bothauthentication and validation that the data has not been altered intransit.

Camera SSL encapsulation because picture and video traffic offered byoff-the-shelf networked IP cameras is not secure when traveling over theInternet. The gateway provides for 128-bit SSL encapsulation of the userpicture and video data sent over the internet for complete user securityand privacy.

802.11b/g/n with WPA-2 security to ensure that wireless cameracommunications always takes place using the strongest availableprotection.

An gateway-enabled device is assigned a unique activation key foractivation with an iConnect server. This ensures that only validgateway-enabled devices can be activated for use with the specificinstance of iConnect server in use. Attempts to activate gateway-enableddevices by brute force are detected by the Security Engine. Partnersdeploying gateway-enabled devices have the knowledge that only angateway with the correct serial number and activation key can beactivated for use with an iConnect server. Stolen devices, devicesattempting to masquerade as gateway-enabled devices, and maliciousoutsiders (or insiders as knowledgeable but nefarious customers) cannoteffect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 allows for seamless and secureupdates to the gateway firmware through the iControl MaintenanceApplication on the server 104, providing a transparent, hassle-freemechanism for the service provider to deploy new features and bug fixesto the installed user base. The firmware download mechanism is tolerantof connection loss, power interruption and user interventions (bothintentional and unintentional). Such robustness reduces down time andcustomer support issues. Gateway firmware can be remotely downloadeither for one gateway at a time, a group of gateways, or in batches.

The Automations engine 308 manages the user-defined rules of interactionbetween the different devices (e.g. when door opens turn on the light).Though the automation rules are programmed and reside at theportal/server level, they are cached at the gateway level in order toprovide short latency between device triggers and actions.

DeviceConnect 310 includes definitions of all supported devices (e.g.,cameras, security panels, sensors, etc.) using a standardized plug-inarchitecture. The DeviceConnect module 310 offers an interface that canbe used to quickly add support for any new device as well as enablinginteroperability between devices that use differenttechnologies/protocols. For common device types, pre-defined sub-moduleshave been defined, making supporting new devices of these types eveneasier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules Engine 318 is responsible for executing the user definedschedules (e.g., take a picture every five minutes; every day at 8 amset temperature to 65 degrees Fahrenheit, etc.). Though the schedulesare programmed and reside at the iConnect server level they are sent tothe scheduler within the gateway application. The Schedules Engine 318then interfaces with SensorConnect 312 to ensure that scheduled eventsoccur at precisely the desired time.

The Device Management module 320 is in charge of all discovery,installation and configuration of both wired and wireless IP devices(e.g., cameras, etc.) coupled or connected to the system. Networked IPdevices, such as those used in the integrated security system, requireuser configuration of many IP and security parameters—to simplify theuser experience and reduce the customer support burden, the devicemanagement module of an embodiment handles the details of thisconfiguration. The device management module also manages the videorouting module described below.

The video routing engine 322 is responsible for delivering seamlessvideo streams to the user with zero-configuration. Through a multi-step,staged approach the video routing engine uses a combination of UPnPport-forwarding, relay server routing and STUN/TURN peer-to-peerrouting.

FIG. 4 is a block diagram of components of the gateway 102, under anembodiment. Depending on the specific set of functionality desired bythe service provider deploying the integrated security system service,the gateway 102 can use any of a number of processors 402, due to thesmall footprint of the gateway application firmware. In an embodiment,the gateway could include the Broadcom BCM5354 as the processor forexample. In addition, the gateway 102 includes memory (e.g., FLASH 404,RAM 406, etc.) and any number of input/output (I/O) ports 408.

Referring to the WAN portion 410 of the gateway 102, the gateway 102 ofan embodiment can communicate with the iConnect server using a number ofcommunication types and/or protocols, for example Ethernet 412,GPRS/CDMA 414 and/or Public Switched Telephone Network (PTSN) 416 toname a few. In general, Ethernet 412 is the primary means of connectionbetween the gateway 102 and the iConnect server 104 and the GPRS/CDMA414 and/or PSTN 416 interfaces acts as back-up for fault tolerance incase the user's broadband connection fails for whatever reason, but theembodiment is not so limited.

Referring to the LAN portion 420 of the gateway 102, various protocolsand physical transceivers can be used to communicate to off-the-shelfsensors and cameras. The gateway 102 is protocol-agnostic andtechnology-agnostic and as such can easily support almost any devicenetworking protocol. The gateway 102 can, for example, support GE andHoneywell security RF protocols 422, Z-Wave 424, serial (RS232 andRS485) 426 for direct connection to security panels as well as WiFi 428(802.11b/g) for communication to WiFi cameras.

The integrated security system includes couplings or connections among avariety of IP devices or components, and the device management module isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system of an embodiment uses a “sandbox” network todiscover and manage all IP devices coupled or connected as components ofthe system. The IP devices of an embodiment include wired devices,wireless devices, cameras, interactive touchscreens, and security panelsto name a few. These devices can be wired via ethernet cable or Wifidevices, all of which are secured within the sandbox network, asdescribed below. The “sandbox” network is described in detail below.

FIG. 5 is a block diagram 500 of network or premises device integrationwith a LAN 570, under an embodiment. In an embodiment, network devices555-557 are coupled to the gateway 102 using a secure network couplingor connection such as SSL over an encrypted 802.11 link (utilizing forexample WPA-2 security for the wireless encryption). The networkcoupling or connection between the gateway 102 and the network devices555-557 is a private coupling or connection in that it is segregatedfrom any other network couplings or connections. The gateway 102 iscoupled to the premises router/firewall 552 via a coupling with apremises LAN 570. The premises router/firewall 552 is coupled to abroadband modem 551, and the broadband modem 551 is coupled to a WAN 560or other network outside the premises. The gateway 102 thus enables orforms a separate wireless network, or sub-network, that includes somenumber of devices and is coupled or connected to the LAN 570 of the hostpremises. The gateway sub-network can include, but is not limited to,any number of other devices like WiFi IP cameras, security panels (e.g.,IP-enabled), and security touchscreens, to name a few. The gateway 102manages or controls the sub-network separately from the LAN 570 andtransfers data and information between components of the sub-network andthe LAN 570/WAN 560, but is not so limited. Additionally, other networkdevices can be coupled to the LAN 570 without being coupled to thegateway 102.

FIG. 6 is a block diagram 600 of network or premises device integrationwith a LAN 570, under an alternative embodiment. The network or premisesdevices 555-557 are coupled to the gateway 102. The network coupling orconnection between the gateway 102 and the network devices 555-557 is aprivate coupling or connection in that it is segregated from any othernetwork couplings or connections. The gateway 102 is coupled orconnected between the premises router/firewall 552 and the broadbandmodem 551. The broadband modem 551 is coupled to a WAN 560 or othernetwork outside the premises, while the premises router/firewall 552 iscoupled to a premises LAN 570. As a result of its location between thebroadband modem 551 and the premises router/firewall 552, the gateway102 can be configured or function as the premises router routingspecified data between the outside network (e.g., WAN 560) and thepremises router/firewall 552 of the LAN 570. As described above, thegateway 102 in this configuration enables or forms a separate wirelessnetwork, or sub-network, that includes the network or premises devices555-557 and is coupled or connected between the LAN 570 of the hostpremises and the WAN 560. The gateway sub-network can include, but isnot limited to, any number of network or premises devices 555-557 likeWiFi IP cameras, security panels (e.g., IP-enabled), and securitytouchscreens, to name a few. The gateway 102 manages or controls thesub-network separately from the LAN 570 and transfers data andinformation between components of the sub-network and the LAN 570/WAN560, but is not so limited. Additionally, other network devices can becoupled to the LAN 570 without being coupled to the gateway 102.

The examples described above with reference to FIGS. 5 and 6 arepresented only as examples of IP device integration. The integratedsecurity system is not limited to the type, number and/or combination ofIP devices shown and described in these examples, and any type, numberand/or combination of IP devices is contemplated within the scope ofthis disclosure as capable of being integrated with the premisesnetwork.

The integrated security system of an embodiment includes a touchscreen(also referred to as the iControl touchscreen or integrated securitysystem touchscreen), as described above, which provides core securitykeypad functionality, content management and presentation, and embeddedsystems design. The networked security touchscreen system of anembodiment enables a consumer or security provider to easily andautomatically install, configure and manage the security system andtouchscreen located at a customer premises. Using this system thecustomer may access and control the local security system, local IPdevices such as cameras, local sensors and control devices (such aslighting controls or pipe freeze sensors), as well as the local securitysystem panel and associated security sensors (such as door/window,motion, and smoke detectors). The customer premises may be a home,business, and/or other location equipped with a wired or wirelessbroadband IP connection.

The system of an embodiment includes a touchscreen with a configurablesoftware user interface and/or a gateway device (e.g., iHub) thatcouples or connects to a premises security panel through a wired orwireless connection, and a remote server that provides access to contentand information from the premises devices to a user when they are remotefrom the home. The touchscreen supports broadband and/or WAN wirelessconnectivity. In this embodiment, the touchscreen incorporates an IPbroadband connection (e.g., Wifi radio, Ethernet port, etc.), and/or acellular radio (e.g., GPRS/GSM, CDMA, WiMax, etc.). The touchscreendescribed herein can be used as one or more of a security systeminterface panel and a network user interface (UI) that provides aninterface to interact with a network (e.g., LAN, WAN, internet, etc.).

The touchscreen of an embodiment provides an integrated touchscreen andsecurity panel as an all-in-one device. Once integrated using thetouchscreen, the touchscreen and a security panel of a premises securitysystem become physically co-located in one device, and the functionalityof both may even be co-resident on the same CPU and memory (though thisis not required).

The touchscreen of an embodiment also provides an integrated IP videoand touchscreen UI. As such, the touchscreen supports one or morestandard video CODECs/players (e.g., H.264, Flash Video, MOV, MPEG4,MJPEG, etc.). The touchscreen UI then provides a mechanism (such as acamera or video widget) to play video. In an embodiment the video isstreamed live from an IP video camera. In other embodiments the videocomprises video clips or photos sent from an IP camera or from a remotelocation.

The touchscreen of an embodiment provides a configurable user interfacesystem that includes a configuration supporting use as a securitytouchscreen. In this embodiment, the touchscreen utilizes a modular userinterface that allows components to be modified easily by a serviceprovider, an installer, or even the end user. Examples of such a modularapproach include using Flash widgets, HTML-based widgets, or otherdownloadable code modules such that the user interface of thetouchscreen can be updated and modified while the application isrunning. In an embodiment the touchscreen user interface modules can bedownloaded over the internet. For example, a new security configurationwidget can be downloaded from a standard web server, and the touchscreenthen loads such configuration app into memory, and inserts it in placeof the old security configuration widget. The touchscreen of anembodiment is configured to provide a self-install user interface.

Embodiments of the networked security touchscreen system describedherein include a touchscreen device with a user interface that includesa security toolbar providing one or more functions including arm,disarm, panic, medic, and alert. The touchscreen therefore includes atleast one screen having a separate region of the screen dedicated to asecurity toolbar. The security toolbar of an embodiment is present inthe dedicated region at all times that the screen is active.

The touchscreen of an embodiment includes a home screen having aseparate region of the screen allocated to managing home-basedfunctions. The home-based functions of an embodiment include managing,viewing, and/or controlling IP video cameras. In this embodiment,regions of the home screen are allocated in the form of widget icons;these widget icons (e.g. for cameras, thermostats, lighting, etc)provide functionality for managing home systems. So, for example, adisplayed camera icon, when selected, launches a Camera Widget, and theCamera widget in turn provides access to video from one or more cameras,as well as providing the user with relevant camera controls (take apicture, focus the camera, etc.)

The touchscreen of an embodiment includes a home screen having aseparate region of the screen allocated to managing, viewing, and/orcontrolling internet-based content or applications. For example, theWidget Manager UI presents a region of the home screen (up to andincluding the entire home screen) where internet widgets icons such asweather, sports, etc. may be accessed). Each of these icons may beselected to launch their respective content services.

The touchscreen of an embodiment is integrated into a premises networkusing the gateway, as described above. The gateway as described hereinfunctions to enable a separate wireless network, or sub-network, that iscoupled, connected, or integrated with another network (e.g., WAN, LANof the host premises, etc.). The sub-network enabled by the gatewayoptimizes the installation process for IP devices, like the touchscreen,that couple or connect to the sub-network by segregating these IPdevices from other such devices on the network. This segregation of theIP devices of the sub-network further enables separate security andprivacy policies to be implemented for these IP devices so that, wherethe IP devices are dedicated to specific functions (e.g., security), thesecurity and privacy policies can be tailored specifically for thespecific functions. Furthermore, the gateway and the sub-network itforms enables the segregation of data traffic, resulting in faster andmore efficient data flow between components of the host network,components of the sub-network, and between components of the sub-networkand components of the network.

The touchscreen of an embodiment includes a core functional embeddedsystem that includes an embedded operating system, required hardwaredrivers, and an open system interface to name a few. The core functionalembedded system can be provided by or as a component of a conventionalsecurity system (e.g., security system available from GE Security).These core functional units are used with components of the integratedsecurity system as described herein. Note that portions of thetouchscreen description below may include reference to a host premisessecurity system (e.g., GE security system), but these references areincluded only as an example and do not limit the touchscreen tointegration with any particular security system.

As an example, regarding the core functional embedded system, a reducedmemory footprint version of embedded Linux forms the core operatingsystem in an embodiment, and provides basic TCP/IP stack and memorymanagement functions, along with a basic set of low-level graphicsprimitives. A set of device drivers is also provided or included thatoffer low-level hardware and network interfaces. In addition to thestandard drivers, an interface to the RS 485 bus is included thatcouples or connects to the security system panel (e.g., GE Concordpanel). The interface may, for example, implement the Superbus 2000protocol, which can then be utilized by the more comprehensivetransaction-level security functions implemented in PanelConnecttechnology (e.g., SetAlarmLevel (int level, int partition, char*accessCode)). Power control drivers are also provided.

FIG. 7 is a block diagram of a touchscreen 700 of the integratedsecurity system, under an embodiment. The touchscreen 700 generallyincludes an application/presentation layer 702 with a residentapplication 704, and a core engine 706. The touchscreen 700 alsoincludes one or more of the following, but is not so limited:applications of premium services 710, widgets 712, a caching proxy 714,network security 716, network interface 718, security object 720,applications supporting devices 722, PanelConnect API 724, a gatewayinterface 726, and one or more ports 728.

More specifically, the touchscreen, when configured as a home securitydevice, includes but is not limited to the following application orsoftware modules: RS 485 and/or RS-232 bus security protocols toconventional home security system panel (e.g., GE Concord panel);functional home security classes and interfaces (e.g. Panel ARM state,Sensor status, etc.); Application/Presentation layer or engine; ResidentApplication; Consumer Home Security Application; installer home securityapplication; core engine; and System bootloader/Software Updater. Thecore Application engine and system bootloader can also be used tosupport other advanced content and applications. This provides aseamless interaction between the premises security application and otheroptional services such as weather widgets or IP cameras.

An alternative configuration of the touchscreen includes a firstApplication engine for premises security and a second Application enginefor all other applications. The integrated security system applicationengine supports content standards such as HTML, XML, Flash, etc. andenables a rich consumer experience for all ‘widgets’, whethersecurity-based or not. The touchscreen thus provides service providersthe ability to use web content creation and management tools to buildand download any ‘widgets’ regardless of their functionality.

As discussed above, although the Security Applications have specificlow-level functional requirements in order to interface with thepremises security system, these applications make use of the samefundamental application facilities as any other ‘widget’, applicationfacilities that include graphical layout, interactivity, applicationhandoff, screen management, and network interfaces, to name a few.

Content management in the touchscreen provides the ability to leverageconventional web development tools, performance optimized for anembedded system, service provider control of accessible content, contentreliability in a consumer device, and consistency between ‘widgets’ andseamless widget operational environment. In an embodiment of theintegrated security system, widgets are created by web developers andhosted on the integrated security system Content Manager (and stored inthe Content Store database). In this embodiment the server componentcaches the widgets and offers them to consumers through the web-basedintegrated security system provisioning system. The servers interactwith the advanced touchscreen using HTTPS interfaces controlled by thecore engine and dynamically download widgets and updates as needed to becached on the touchscreen. In other embodiments widgets can be accesseddirectly over a network such as the Internet without needing to gothrough the iControl Content Manager

Referring to FIG. 7 , the touchscreen system is built on a tieredarchitecture, with defined interfaces between theApplication/Presentation Layer (the Application Engine) on the top, theCore Engine in the middle, and the security panel and gateway APIs atthe lower level. The architecture is configured to provide maximumflexibility and ease of maintenance.

The application engine of the touchscreen provides the presentation andinteractivity capabilities for all applications (widgets) that run onthe touchscreen, including both core security function widgets and thirdparty content widgets. FIG. 8 is an example screenshot 800 of anetworked security touchscreen, under an embodiment. This examplescreenshot 800 includes three interfaces or user interface (UI)components 802-806, but is not so limited. A first UI 802 of thetouchscreen includes icons by which a user controls or accessesfunctions and/or components of the security system (e.g., “Main”,“Panic”, “Medic”, “Fire”, state of the premises alarm system (e.g.,disarmed, armed, etc.), etc.); the first UI 802, which is also referredto herein as a security interface, is always presented on thetouchscreen. A second UI 804 of the touchscreen includes icons by whicha user selects or interacts with services and other network content(e.g., clock, calendar, weather, stocks, news, sports, photos, maps,music, etc.) that is accessible via the touchscreen. The second UI 804is also referred to herein as a network interface or content interface.A third UI 806 of the touchscreen includes icons by which a user selectsor interacts with additional services or components (e.g., intercomcontrol, security, cameras coupled to the system in particular regions(e.g., front door, baby, etc.) available via the touchscreen.

A component of the application engine is the Presentation Engine, whichincludes a set of libraries that implement the standards-based widgetcontent (e.g., XML, HTML, JavaScript, Flash) layout and interactivity.This engine provides the widget with interfaces to dynamically load bothgraphics and application logic from third parties, support high leveldata description language as well as standard graphic formats. The setof web content-based functionality available to a widget developer isextended by specific touchscreen functions implemented as local webservices by the Core Engine.

The resident application of the touchscreen is the master service thatcontrols the interaction of all widgets in the system, and enforces thebusiness and security rules required by the service provider. Forexample, the resident application determines the priority of widgets,thereby enabling a home security widget to override resource requestsfrom a less critical widget (e.g. a weather widget). The residentapplication also monitors widget behavior, and responds to client orserver requests for cache updates.

The core engine of the touchscreen manages interaction with othercomponents of the integrated security system, and provides an interfacethrough which the resident application and authorized widgets can getinformation about the home security system, set alarms, install sensors,etc. At the lower level, the Core Engine's main interactions are throughthe PanelConnect API, which handles all communication with the securitypanel, and the gateway Interface, which handles communication with thegateway. In an embodiment, both the iHub Interface and PanelConnect APIare resident and operating on the touchscreen. In another embodiment,the PanelConnect API runs on the gateway or other device that providessecurity system interaction and is accessed by the touchscreen through aweb services interface.

The Core Engine also handles application and service level persistentand cached memory functions, as well as the dynamic provisioning ofcontent and widgets, including but not limited to: flash memorymanagement, local widget and content caching, widget version management(download, cache flush new/old content versions), as well as the cachingand synchronization of user preferences. As a portion of these servicesthe Core engine incorporates the bootloader functionality that isresponsible for maintaining a consistent software image on thetouchscreen, and acts as the client agent for all software updates. Thebootloader is configured to ensure full update redundancy so thatunsuccessful downloads cannot corrupt the integrated security system.

Video management is provided as a set of web services by the CoreEngine. Video management includes the retrieval and playback of localvideo feeds as well as remote control and management of cameras (allthrough iControl CameraConnect technology).

Both the high level application layer and the mid-level core engine ofthe touchscreen can make calls to the network. Any call to the networkmade by the application layer is automatically handed off to a localcaching proxy, which determines whether the request should be handledlocally. Many of the requests from the application layer are webservices API requests; although such requests could be satisfied by theiControl servers, they are handled directly by the touchscreen and thegateway. Requests that get through the caching proxy are checked againsta white list of acceptable sites, and, if they match, are sent offthrough the network interface to the gateway. Included in the NetworkSubsystem is a set of network services including HTTP, HTTPS, andserver-level authentication functions to manage the secure client-serverinterface. Storage and management of certificates is incorporated as apart of the network services layer.

Server components of the integrated security system servers supportinteractive content services on the touchscreen. These server componentsinclude, but are not limited to the content manager, registry manager,network manager, and global registry, each of which is described herein.

The Content Manager oversees aspects of handling widget data and rawcontent on the touchscreen. Once created and validated by the serviceprovider, widgets are ‘ingested’ to the Content Manager, and then becomeavailable as downloadable services through the integrated securitysystem Content Management APIs. The Content manager maintains versionsand timestamp information, and connects to the raw data contained in thebackend Content Store database. When a widget is updated (or new contentbecomes available) all clients registering interest in a widget aresystematically updated as needed (a process that can be configured at anaccount, locale, or system-wide level).

The Registry Manager handles user data, and provisioning accounts,including information about widgets the user has decided to install, andthe user preferences for these widgets.

The Network Manager handles getting and setting state for all devices onthe integrated security system network (e.g., sensors, panels, cameras,etc.). The Network manager synchronizes with the gateway, the advancedtouchscreen, and the subscriber database.

The Global Registry is a primary starting point server for all clientservices, and is a logical referral service that abstracts specificserver locations/addresses from clients (touchscreen, gateway 102,desktop widgets, etc.). This approach enables easy scaling/migration ofserver farms.

The touchscreen of an embodiment operates wirelessly with a premisessecurity system. The touchscreen of an embodiment incorporates an RFtransceiver component that either communicates directly with the sensorsand/or security panel over the panel's proprietary RF frequency, or thetouchscreen communicates wirelessly to the gateway over 802.11,Ethernet, or other IP-based communications channel, as described indetail herein. In the latter case the gateway implements thePanelConnect interface and communicates directly to the security paneland/or sensors over wireless or wired networks as described in detailabove.

The touchscreen of an embodiment is configured to operate with multiplesecurity systems through the use of an abstracted security systeminterface. In this embodiment, the PanelConnect API can be configured tosupport a plurality of proprietary security system interfaces, eithersimultaneously or individually as described herein. In one embodiment ofthis approach, the touchscreen incorporates multiple physical interfacesto security panels (e.g. GE Security RS-485, Honeywell RF, etc.) inaddition to the PanelConnect API implemented to support multiplesecurity interfaces. The change needed to support this in PanelConnectis a configuration parameter specifying the panel type connection thatis being utilized.

So for example, the setARMState( ) function is called with an additionalparameter (e.g., Armstate=setARMState(type=“ARM STAY|ARM AWAY|DISARM”,Parameters=“ExitDelay=30|Lights=OFF”, panelType=“GE Concord4 RS485”)).The ‘panelType’ parameter is used by the setARMState function (and inpractice by all of the PanelConnect functions) to select an algorithmappropriate to the specific panel out of a plurality of algorithms.

The touchscreen of an embodiment is self-installable. Consequently, thetouchscreen provides a ‘wizard’ approach similar to that used intraditional computer installations (e.g. InstallShield). The wizard canbe resident on the touchscreen, accessible through a web interface, orboth. In one embodiment of a touchscreen self-installation process, theservice provider can associate devices (sensors, touchscreens, securitypanels, lighting controls, etc.) remotely using a web-basedadministrator interface.

The touchscreen of an embodiment includes a battery backup system for asecurity touchscreen. The touchscreen incorporates a standard Li-ion orother battery and charging circuitry to allow continued operation in theevent of a power outage. In an embodiment the battery is physicallylocated and connected within the touchscreen enclosure. In anotherembodiment the battery is located as a part of the power transformer, orin between the power transformer and the touchscreen.

The example configurations of the integrated security system describedabove with reference to FIGS. 5 and 6 include a gateway that is aseparate device, and the touchscreen couples to the gateway. However, inan alternative embodiment, the gateway device and its functionality canbe incorporated into the touchscreen so that the device managementmodule, which is now a component of or included in the touchscreen, isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system with the integrated touchscreen/gateway usesthe same “sandbox” network to discover and manage all IP devices coupledor connected as components of the system.

The touchscreen of this alternative embodiment integrates the componentsof the gateway with the components of the touchscreen as describedherein. More specifically, the touchscreen of this alternativeembodiment includes software or applications described above withreference to FIG. 3 . In this alternative embodiment, the touchscreenincludes the gateway application layer 302 as the main program thatorchestrates the operations performed by the gateway. A Security Engine304 of the touchscreen provides robust protection against intentionaland unintentional intrusion into the integrated security system networkfrom the outside world (both from inside the premises as well as fromthe WAN). The Security Engine 304 of an embodiment comprises one or moresub-modules or components that perform functions including, but notlimited to, the following:

Encryption including 128-bit SSL encryption for gateway and iConnectserver communication to protect user data privacy and provide securecommunication.

Bi-directional authentication between the touchscreen and iConnectserver in order to prevent unauthorized spoofing and attacks. Data sentfrom the iConnect server to the gateway application (or vice versa) isdigitally signed as an additional layer of security. Digital signingprovides both authentication and validation that the data has not beenaltered in transit.

Camera SSL encapsulation because picture and video traffic offered byoff-the-shelf networked IP cameras is not secure when traveling over theInternet. The touchscreen provides for 128-bit SSL encapsulation of theuser picture and video data sent over the internet for complete usersecurity and privacy.

802.11b/g/n with WPA-2 security to ensure that wireless cameracommunications always takes place using the strongest availableprotection.

A touchscreen-enabled device is assigned a unique activation key foractivation with an iConnect server. This ensures that only validgateway-enabled devices can be activated for use with the specificinstance of iConnect server in use. Attempts to activate gateway-enableddevices by brute force are detected by the Security Engine. Partnersdeploying touchscreen-enabled devices have the knowledge that only agateway with the correct serial number and activation key can beactivated for use with an iConnect server. Stolen devices, devicesattempting to masquerade as gateway-enabled devices, and maliciousoutsiders (or insiders as knowledgeable but nefarious customers) cannoteffect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 of the touchscreen allows forseamless and secure updates to the gateway firmware through the iControlMaintenance Application on the server 104, providing a transparent,hassle-free mechanism for the service provider to deploy new featuresand bug fixes to the installed user base. The firmware downloadmechanism is tolerant of connection loss, power interruption and userinterventions (both intentional and unintentional). Such robustnessreduces down time and customer support issues. Touchscreen firmware canbe remotely download either for one touchscreen at a time, a group oftouchscreen, or in batches.

The Automations engine 308 of the touchscreen manages the user-definedrules of interaction between the different devices (e.g. when door opensturn on the light). Though the automation rules are programmed andreside at the portal/server level, they are cached at the gateway levelin order to provide short latency between device triggers and actions.

DeviceConnect 310 of the touchscreen includes definitions of allsupported devices (e.g., cameras, security panels, sensors, etc.) usinga standardized plug-in architecture. The DeviceConnect module 310 offersan interface that can be used to quickly add support for any new deviceas well as enabling interoperability between devices that use differenttechnologies/protocols. For common device types, pre-defined sub-moduleshave been defined, making supporting new devices of these types eveneasier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules Engine 318 of the touchscreen is responsible for executingthe user defined schedules (e.g., take a picture every five minutes;every day at 8 am set temperature to 65 degrees Fahrenheit, etc.).Though the schedules are programmed and reside at the iConnect serverlevel they are sent to the scheduler within the gateway application ofthe touchscreen. The Schedules Engine 318 then interfaces withSensorConnect 312 to ensure that scheduled events occur at precisely thedesired time.

The Device Management module 320 of the touchscreen is in charge of alldiscovery, installation and configuration of both wired and wireless IPdevices (e.g., cameras, etc.) coupled or connected to the system.Networked IP devices, such as those used in the integrated securitysystem, require user configuration of many IP and security parameters,and the device management module of an embodiment handles the details ofthis configuration. The device management module also manages the videorouting module described below.

The video routing engine 322 of the touchscreen is responsible fordelivering seamless video streams to the user with zero-configuration.Through a multi-step, staged approach the video routing engine uses acombination of UPnP port-forwarding, relay server routing and STUN/TURNpeer-to-peer routing.

FIG. 9 is a block diagram 900 of network or premises device integrationwith a LAN 570, under an embodiment. In an embodiment, network devices555, 556, 957 are coupled to the touchscreen 902 using a secure networkconnection such as SSL over an encrypted 802.11 link (utilizing forexample WPA-2 security for the wireless encryption), and the touchscreen902 coupled to the premises router/firewall 552 via a coupling with apremises LAN 570. The premises router/firewall 552 is coupled to abroadband modem 551, and the broadband modem 551 is coupled to a WAN 560or other network outside the premises. The touchscreen 902 thus enablesor forms a separate wireless network, or sub-network, that includes somenumber of devices and is coupled or connected to the LAN 570 of the hostpremises. The touchscreen sub-network can include, but is not limitedto, any number of other devices like WiFi IP cameras, security panels(e.g., IP-enabled), and IP devices, to name a few. The touchscreen 902manages or controls the sub-network separately from the LAN 570 andtransfers data and information between components of the sub-network andthe LAN 570/WAN 560, but is not so limited. Additionally, other networkdevices can be coupled to the LAN 570 without being coupled to thetouchscreen 902.

FIG. 10 is a block diagram 1000 of network or premises deviceintegration with a LAN 570, under an alternative embodiment. The networkor premises devices 555, 556, 1057 are coupled to the touchscreen 1002,and the touchscreen 1002 is coupled or connected between the premisesrouter/firewall 552 and the broadband modem 551. The broadband modem 551is coupled to a WAN 560 or other network outside the premises, while thepremises router/firewall 552 is coupled to a premises LAN 570. As aresult of its location between the broadband modem 551 and the premisesrouter/firewall 552, the touchscreen 1002 can be configured or functionas the premises router routing specified data between the outsidenetwork (e.g., WAN 560) and the premises router/firewall 552 of the LAN570. As described above, the touchscreen 1002 in this configurationenables or forms a separate wireless network, or sub-network, thatincludes the network or premises devices 555, 556, 1057 and is coupledor connected between the LAN 570 of the host premises and the WAN 560.The touchscreen sub-network can include, but is not limited to, anynumber of network or premises devices 555, 556, 1057 like WiFi IPcameras, security panels (e.g., IP-enabled), and security touchscreens,to name a few. The touchscreen 1002 manages or controls the sub-networkseparately from the LAN 570 and transfers data and information betweencomponents of the sub-network and the LAN 570/WAN 560, but is not solimited. Additionally, other network devices can be coupled to the LAN570 without being coupled to the touchscreen 1002.

The gateway of an embodiment, whether a stand-along component orintegrated with a touchscreen, enables couplings or connections and thusthe flow or integration of information between various components of thehost premises and various types and/or combinations of IP devices, wherethe components of the host premises include a network (e.g., LAN) and/ora security system or subsystem to name a few. Consequently, the gatewaycontrols the association between and the flow of information or databetween the components of the host premises. For example, the gateway ofan embodiment forms a sub-network coupled to another network (e.g., WAN,LAN, etc.), with the sub-network including IP devices. The gatewayfurther enables the association of the IP devices of the sub-networkwith appropriate systems on the premises (e.g., security system, etc.).Therefore, for example, the gateway can form a sub-network of IP devicesconfigured for security functions, and associate the sub-network onlywith the premises security system, thereby segregating the IP devicesdedicated to security from other IP devices that may be coupled toanother network on the premises.

In an example embodiment, FIG. 11 is a flow diagram 1100 for integrationor installation of an IP device into a private network environment,under an embodiment. The IP device includes any IP-capable device which,for example, includes the touchscreen of an embodiment. The variables ofan embodiment set at time of installation include, but are not limitedto, one or more of a private SSID/Password, an gateway identifier, asecurity panel identifier, a user account TS, and a Central MonitoringStation account identification.

An embodiment of the IP device discovery and management begins with auser or installer activating 1102 the gateway and initiating 1104 theinstall mode of the system. This places the gateway in an install mode.Once in install mode, the gateway shifts to a default (Install) Wificonfiguration. This setting will match the default setting for otherintegrated security system-enabled devices that have been pre-configuredto work with the integrated security system. The gateway will then beginto provide 1106 DHCP addresses for these IP devices. Once the deviceshave acquired a new DHCP address from the gateway, those devices areavailable for configuration into a new secured Wifi network setting.

The user or installer of the system selects 1108 all devices that havebeen identified as available for inclusion into the integrated securitysystem. The user may select these devices by their unique IDs via a webpage, Touchscreen, or other client interface. The gateway provides 1110data as appropriate to the devices. Once selected, the devices areconfigured 1112 with appropriate secured Wifi settings, including SSIDand WPA/WPA-2 keys that are used once the gateway switches back to thesecured sandbox configuration from the “Install” settings. Othersettings are also configured as appropriate for that type of device.Once all devices have been configured, the user is notified and the usercan exit install mode. At this point all devices will have beenregistered 1114 with the integrated security system servers.

The installer switches 1116 the gateway to an operational mode, and thegateway instructs or directs 1118 all newly configured devices to switchto the “secured” Wifi sandbox settings. The gateway then switches 1120to the “secured” Wifi settings. Once the devices identify that thegateway is active on the “secured” network, they request new DHCPaddresses from the gateway which, in response, provides 1122 the newaddresses. The devices with the new addresses are then operational 1124on the secured network.

In order to ensure the highest level of security on the secured network,the gateway can create or generate a dynamic network securityconfiguration based on the unique ID and private key in the gateway,coupled with a randomizing factor that can be based on online time orother inputs. This guarantees the uniqueness of the gateway securednetwork configuration.

To enable the highest level of performance, the gateway analyzes the RFspectrum of the 802.11x network and determines which frequencyband/channel it should select to run.

An alternative embodiment of the camera/IP device management processleverages the local ethernet connection of the sandbox network on thegateway. This alternative process is similar to the Wifi discoveryembodiment described above, except the user connects the targeted deviceto the ethernet port of the sandbox network to begin the process. Thisalternative embodiment accommodates devices that have not beenpre-configured with the default “Install” configuration for theintegrated security system.

This alternative embodiment of the IP device discovery and managementbegins with the user/installer placing the system into install mode. Theuser is instructed to attach an IP device to be installed to the sandboxEthernet port of the gateway. The IP device requests a DHCP address fromthe gateway which, in response to the request, provides the address. Theuser is presented the device and is asked if he/she wants to install thedevice. If yes, the system configures the device with the secured Wifisettings and other device-specific settings (e.g., camera settings forvideo length, image quality etc.). The user is next instructed todisconnect the device from the ethernet port. The device is nowavailable for use on the secured sandbox network.

FIG. 12 is a block diagram showing communications among integrated IPdevices of the private network environment, under an embodiment. The IPdevices of this example include a security touchscreen 1203, gateway1202 (e.g., “iHub”), and security panel (e.g., “Security Panel 1”,“Security Panel 2”, “Security Panel n”), but the embodiment is not solimited. In alternative embodiments any number and/or combination ofthese three primary component types may be combined with othercomponents including IP devices and/or security system components. Forexample, a single device which comprises an integrated gateway,touchscreen, and security panel is merely another embodiment of theintegrated security system described herein. The description thatfollows includes an example configuration that includes a touchscreenhosting particular applications. However, the embodiment is not limitedto the touchscreen hosting these applications, and the touchscreenshould be thought of as representing any IP device.

Referring to FIG. 12 , the touchscreen 1203 incorporates a touchscreencore application 1210 that is implemented as computer code resident onthe touchscreen operating system, or as a web-based application runningin a browser, or as another type of scripted application (e.g., Flash,Java, Visual Basic, etc.). The touchscreen core application 1210represents this application, providing user interface and logic for theend user to manage their security system or to gain access to networkedinformation or content (Widgets). The touchscreen core application 1210in turn accesses a library or libraries of functions to control thelocal hardware (e.g. screen display, sound, LEDs, memory, etc.) as wellas specialized librarie(s) to couple or connect to the security system.

In an embodiment of this security system connection, the touchscreen1203 communicates to the gateway 1202, and has no direct communicationwith the security panel. In this embodiment, the touchscreen coreapplication 1210 accesses the remote service APIs 1212 which providesecurity system functionality (e.g. ARM/DISARM panel, sensor state,get/set panel configuration parameters, initiate or get alarm events,etc.). In an embodiment, the remote service APIs 1212 implement one ormore of the following functions, but the embodiment is not so limited:Armstate=setARMState(type=“ARM STAY|ARM AWAY|DISARM”,Parameters=“ExitDelay=30|Lights=OFF”); sensorState=getSensors(type=“ALL|SensorName|SensorNameList”); result=setSensorState(SensorName,parameters=“Option1, Options2, . . . Option n”);interruptHandler=SensorEvent( ); and, interruptHandler=alarmEvent( ).

Functions of the remote service APIs 1212 of an embodiment use a remotePanelConnect API 1224 which resides in memory on the gateway 1202. Thetouchscreen 1203 communicates with the gateway 1202 through a suitablenetwork interface such as an Ethernet or 802.11 RF connection, forexample. The remote PanelConnect API 1224 provides the underlyingSecurity System Interfaces 1226 used to communicate with and control oneor more types of security panel via wired link 1230 and/or RF link 3.The PanelConnect API 1224 provides responses and input to the remoteservices APIs 1212, and in turn translates function calls and data toand from the specific protocols and functions supported by a specificimplementation of a Security Panel (e.g. a GE Security Simon XT orHoneywell Vista 20P). In an embodiment, the PanelConnect API 1224 uses a345 MHz RF transceiver or receiver hardware/firmware module tocommunicate wirelessly to the security panel and directly to a set of345 MHz RF-enabled sensors and devices, but the embodiment is not solimited.

The gateway of an alternative embodiment communicates over a wiredphysical coupling or connection to the security panel using the panel'sspecific wired hardware (bus) interface and the panel's bus-levelprotocol.

In an alternative embodiment, the Touchscreen 1203 implements the samePanelConnect API 1214 locally on the Touchscreen 1203, communicatingdirectly with the Security Panel 2 and/or Sensors 2 over the proprietaryRF link or over a wired link for that system. In this embodiment theTouchscreen 1203, instead of the gateway 1202, incorporates the 345 MHzRF transceiver to communicate directly with Security Panel 2 or Sensors2 over the RF link 2. In the case of a wired link the Touchscreen 1203incorporates the real-time hardware (e.g. a PIC chip and RS232-variantserial link) to physically connect to and satisfy the specific bus-leveltiming requirements of the SecurityPanel2.

In yet another alternative embodiment, either the gateway 1202 or theTouchscreen 1203 implements the remote service APIs. This embodimentincludes a Cricket device (“Cricket”) which comprises but is not limitedto the following components: a processor (suitable for handling 802.11protocols and processing, as well as the bus timing requirements ofSecurityPanel1); an 802.11 (WiFi) client IP interface chip; and, aserial bus interface chip that implements variants of RS232 or RS485,depending on the specific Security Panel.

The Cricket also implements the full PanelConnect APIs such that it canperform the same functions as the case where the gateway implements thePanelConnect APIs. In this embodiment, the touchscreen core application1210 calls functions in the remote service APIs 1212 (such assetArmState( )). These functions in turn couple or connect to the remoteCricket through a standard IP connection (“Cricket IP Link”) (e.g.,Ethernet, Homeplug, the gateway's proprietary Wifi network, etc.). TheCricket in turn implements the PanelConnect API, which responds to therequest from the touchscreen core application, and performs theappropriate function using the proprietary panel interface. Thisinterface uses either the wireless or wired proprietary protocol for thespecific security panel and/or sensors.

Components of the gateway of the integrated security system describedherein control discovery, installation and configuration of both wiredand wireless IP devices (e.g., cameras, etc.) coupled or connected tothe system, as described above with reference to FIGS. 1-4 , as well asmanagement of video routing using a video routing module or engine. Thevideo routing engine initiates communication paths for the transfer ofvideo from a streaming source device to a requesting client device, anddelivers seamless video streams to the user via the communication pathsusing one or more of UPnP port-forwarding, relay server routing andSTUN/TURN peer-to-peer routing, each of which is described below.

By way of reference, conventional video cameras have the ability tostream digital video in a variety of formats and over a variety ofnetworks. Internet protocol (IP) video cameras, which include videocameras using an IP transport network (e.g., Ethernet, WiFi (IEEE 802.11standards), etc.) are prevalent and increasingly being utilized in homemonitoring and security system applications. With the proliferation ofthe internet, Ethernet and WiFi local area networks (LANs) and advancedwide area networks (WANs) that offer high bandwidth, low latencyconnections (broadband), as well as more advanced wireless WAN datanetworks (e.g. GPRS or CDMA 1×RTT), there increasingly exists thenetworking capability to extend traditional security systems to offerIP-based video. However, a fundamental reason for such IP video in asecurity system is to enable a user or security provider to monitor liveor otherwise streamed video from outside the host premises (and theassociated LAN).

The conventional solution to this problem has involved a technique knownas ‘port forwarding’, whereby a ‘port’ on the LAN's router/firewall isassigned to the specific LAN IP address for an IP camera, or a proxy tothat camera. Once a port has been ‘forwarded’ in this manner, a computerexternal to the LAN can address the LAN's router directly, and requestaccess to that port. This access request is then forwarded by the routerdirectly to the IP address specified, the IP camera or proxy. In thisway an external device can directly access an IP camera within the LANand view or control the streamed video.

The issues with this conventional approach include the following: portforwarding is highly technical and most users do not know how/why to doit; automatic port forwarding is difficult and problematic usingemerging standards like UPnP; the camera IP address is often reset inresponse to a power outage/router reboot event; there are many differentrouters with different ways/capabilities for port forwarding. In short,although port forwarding can work, it is frequently less than adequateto support a broadly deployed security solution utilizing IP cameras.

Another approach to accessing streaming video externally to a LANutilizes peer-to-peer networking technology. So-called peer-to-peernetworks, which includes networks in which a device or client isconnected directly to another device or client, typically over a WideArea Network (WAN) and without a persistent server connection, areincreasingly common. In addition to being used for the sharing of filesbetween computers (e.g., Napster and KaZaa), peer-to-peer networks havealso been more recently utilized to facilitate direct audio and mediastreaming in applications such as Skype. In these cases, thepeer-to-peer communications have been utilized to enable telephony-stylevoice communications and video conferencing between two computers, eachenabled with an IP-based microphone, speaker, and video camera. Afundamental reason for adopting such peer-to-peer technology is theability to transparently ‘punch through’ LAN firewalls to enableexternal access to the streaming voice and video content, and to do soin a way that scales to tens of millions of users without creating anuntenable server load.

A limitation of the conventional peer-to-peer video transport lies inthe personal computer (PC)-centric nature of the solution. Each of theconventional solutions uses a highly capable PC connected to the videocamera, with the PC providing the advanced software functionalityrequired to initiate and manage the peer-to-peer connection with theremote client. A typical security or remote home monitoring systemrequires multiple cameras, each with its own unique IP address, and onlya limited amount of processing capability in each camera such that theconventional PC-centric approach cannot easily solve the need. Insteadof a typical PC-centric architecture with three components (a “3-way IPVideo System”) that include a computer device with video camera, amediating server, and a PC client with video display capability, theconventional security system adds a plurality of fourth components thatare standalone IP video cameras (requiring a “4-way IP Video System”),another less-than-ideal solution.

In accordance with the embodiments described herein, IP cameramanagement systems and methods are provided that enable a consumer orsecurity provider to easily and automatically configure and manage IPcameras located at a customer premises. Using this system IP cameramanagement may be extended to remote control and monitoring from outsidethe firewall and router of the customer premises.

With reference to FIGS. 5 and 6 , the system includes a gateway 553having a video routing component so that the gateway 553 can manage andcontrol, or assist in management and control, or video routing. Thesystem also includes one or more cameras (e.g., WiFi IP camera 555,Ethernet IP camera 554, etc.) that communicate over the LAN 570 using anIP format, as well as a connection management server 510 located outsidethe premises firewall 552 and connected to the gateway 553 by a WideArea Network (WAN) 560. The system further includes one or more devices520, 530, 540 located outside the premises and behind other firewalls521, 531, 541 and connected to the WAN 560. The other devices 520, 530,540 are configured to access video or audio content from the IP cameraswithin the premises, as described above.

Alternatively, with reference to FIGS. 9 and 10 , the system includes atouchscreen 902 or 1002 having a video routing component so that thetouchscreen 902 or 1002 can manage and control, or assist in managementand control, or video routing. The system also includes one or morecameras (e.g., WiFi IP camera 555, Ethernet IP camera 554, etc.) thatcommunicate over the LAN 570 using an IP format, as well as a connectionmanagement server 510 located outside the premises firewall 552 andconnected to the gateway 553 by a Wide Area Network (WAN) 560. Thesystem further includes one or more devices 520, 530, 540 locatedoutside the premises and behind other firewalls 521, 531, 541 andconnected to the WAN 560. The other devices 520, 530, 540 are configuredto access video or audio content from the IP cameras within thepremises, as described above.

FIG. 13 is a general flow diagram for IP video control, under anembodiment. The IP video control interfaces, manages, and providesWAN-based remote access to a plurality of IP cameras in conjunction witha home security or remote home monitoring system. The IP video controlallows for monitoring and controlling of IP video cameras from alocation remote to the customer premises, outside the customer premisesfirewall, and protected by another firewall. Operations begin when thesystem is powered on 1310, involving at a minimum the power-on of thegateway, as well as the power-on of at least one IP camera coupled orconnected to the premises LAN. The gateway searches 1311 for availableIP cameras and associated IP addresses. The gateway selects 1312 fromone or more possible approaches to create connections between the IPcamera and a device external to the firewall. Once an appropriateconnection path is selected, the gateway begins operation 1313, andawaits 1320 a request for a stream from one of the plurality of IP videocameras available on the LAN. When a stream request is present theserver retrieves 1321 the requestor's WAN IP address/port.

When a server relay is present 1330, the IP camera is instructed 1331 tostream to the server, and the connection is managed 1332 through theserver. In response to the stream terminating 1351, operations return togateway operation 1313, and waits to receive another request 1320 for astream from one of the plurality of IP video cameras available on theLAN.

When a server relay is not present 1330, the requestor's WAN IPaddress/port is provided 1333 to the gateway or gateway relay. When agateway relay is present 1340, the IP camera is instructed 1341 tostream to the gateway, and the gateway relays 1342 the connection to therequestor. In response to the stream terminating 1351, operations returnto gateway operation 1313, and waits to receive another request 1320 fora stream from one of the plurality of IP video cameras available on theLAN. When a gateway relay is not present 1340, the IP camera isinstructed 1343 to stream to an address, and a handoff 1344 is maderesulting in direct communication between the camera and the requestor.In response to the stream terminating 1351, operations return to gatewayoperation 1313, and waits to receive another request 1320 from one ofthe plurality of IP video cameras available on the LAN.

The integrated security system of an embodiment supports numerous videostream formats or types of video streams. Supported video streamsinclude, but are not limited to, Motion Picture Experts Group (MPEG)-4(MPEG-4)/Real-Time Streaming Protocol (RTSP), MPEG-4 over HypertextTransfer Protocol (HTTP), and Motion Joint Photographic Experts Group(JPEG) (MJPEG).

The integrated security system of an embodiment supports the MPEG-4/RTSPvideo streaming method (supported by video servers and clients) whichuses RTSP for the control channel and Real-time Transport Protocol (RTP)for the data channel. Here the RTSP channel is over Transmission ControlProtocol (TCP) while the data channel uses User Datagram Protocol (UDP).This method is widely supported by both streaming sources (e.g.,cameras) and stream clients (e.g., remote client devices, AppleQuicktime, VideoLAN, IPTV mobile phones, etc.).

Encryption can be added to the two channels under MPEG-4/RTSP. Forexample, the RTSP control channel can be encrypted using SSL/TLS. Thedata channel can also be encrypted.

If the camera or video stream source inside the home does not supportencryption for either RTSP or RTP channels, the gateway located on theLAN can facilitate the encrypted RTSP method by maintaining separate TCPsessions with the video stream source device and with the encrypted RTSPclient outside the LAN, and relay all communication between the twosessions. In this situation, any communication between the gateway andthe video stream source that is not encrypted could be encrypted by thegateway before being relayed to the RTSP client outside the LAN. In manycases the gateway is an access point for the encrypted and private Wifinetwork on which the video stream source device is located. This meansthat communication between the gateway and the video stream sourcedevice is encrypted at the network level, and communication between thegateway and the RTSP client is encrypted at the transport level. In thisfashion the gateway can compensate for a device that does not supportencrypted RTSP.

The integrated security system of an embodiment also supports reverseRTSP. Reverse RTSP includes taking a TCP-based protocol like RTSP, andreversing the roles of client and server (references to “server” includethe iControl server, also referred to as the iConnect server) when itcomes to TCP session establishment. For example, in standard RTSP theRTSP client is the one that establishes the TCP connection with thestream source server (the server listens on a port for incomingconnections). In Reverse RTSP, the RTSP client listens on a port forincoming connections from the stream source server. Once the TCPconnection is established, the RTSP client begins sending commands tothe server over the TCP connection just as it would in standard RTSP.

When using Reverse RTSP, the video stream source is generally on a LAN,protected by a firewall. Having a device on the LAN initiate theconnection to the RTSP client outside the firewall enables easy networktraversal.

If the camera or video stream source inside the LAN does not supportReverse RTSP, then the gateway facilitates the Reverse RTSP method byinitiating separate TCP sessions with the video stream source device andwith the Reverse RTSP client outside the LAN, and then relays allcommunication between the two sessions. In this fashion the gatewaycompensates for a stream source device that does not support ReverseRTSP.

As described in the encryption description above, the gateway canfurther compensate for missing functionalities on the device such asencryption. If the device does not support encryption for either RTSP orRTP channels, the gateway can communicate with the device using theseun-encrypted streams, and then encrypt the streams before relaying themout of the LAN to the RTSP Reverse client.

Servers of the integrated security system can compensate for RTSPclients that do not support Reverse RTSP. In this situation, the serveraccepts TCP connections from both the RTSP client and the Reverse RTSPvideo stream source (which could be a gateway acting on behalf of astream source device that does not support Reverse RTSP). The serverthen relays the control and video streams from the Reverse RTSP videostream source to the RTSP client. The server can further compensate forthe encryption capabilities of the RTSP client; if the RTSP client doesnot support encryption then the server can provide an unencrypted streamto the RTSP client even though an encrypted stream was received from theReverse RTSP streaming video source.

The integrated security system of an embodiment also supports SimpleTraversal of User Datagram Protocol (UDP) through Network AddressTranslators (NAT) (STUN)/Traversal Using Relay NAT (TURN) peer-to-peerrouting. STUN and Turn are techniques for using a server to helpestablish a peer-to-peer UDP data stream (it does not apply to TCPstreams). The bandwidth consumed by the data channel of a video streamis usually many thousands of times larger than that used by the controlchannel. Consequently, when a peer-to-peer connection for both the RTSPand RTP channels is not possible, there is still a great incentive touse STUN/TURN techniques in order to achieve a peer-to-peer connectionfor the RTP data channel.

Here, a method referred to herein as RTSP with STUN/TURN is used by theintegrated security system. The RTSP with STUN/TURN is a method in whichthe video streaming device is instructed over the control channel tostream its UDP data channel to a different network address than that ofthe other end of the control TCP connection (usually the UDP data issimply streamed to the IP address of the RTSP client). The result isthat the RTSP or Reverse RTSP TCP channel can be relayed using thegateway and/or the server, while the RTP UDP data channel can flowdirectly from the video stream source device to the video stream client.

If a video stream source device does not support RTSP with STUN/TURN,the gateway can compensate for the device by relaying the RTSP controlchannel via the server to the RTSP client, and receiving the RTP datachannel and then forwarding it directly to the RTSP with STUN/TURNenabled client. Encryption can also be added here by the gateway.

The integrated security system of an embodiment supports MPEG-4 overHTTP. MPEG-4 over HTTP is similar to MPEG-4 over RTSP except that boththe RTSP control channel and the RTP data channel are passed over anHTTP TCP session. Here a single TCP session can be used, splitting itinto multiple channels using common HTTP techniques like chunkedtransfer encoding.

The MPEG-4 over HTTP is generally supported by many video stream clientsand server devices, and encryption can easily be added to it usingSSL/TLS. Because it uses TCP for both channels, STUN/TURN techniques maynot apply in the event that a direct peer-to-peer TCP session betweenclient and server cannot be established.

As described above, encryption can be provided using SSL/TLS taking theform of HTTPS. And as with MPEG-4 over RTSP, a gateway can compensatefor a stream source device that does not support encryption by relayingthe TCP streams and encrypting the TCP stream between the gateway andthe stream client. In many cases the gateway is an access point for theencrypted and private Wifi network on which the video stream sourcedevice is located. This means that communication between the gateway andthe video stream source device is encrypted at the network level, andcommunication between the gateway and the video stream client isencrypted at the transport level. In this fashion the gateway cancompensate for a device that does not support HTTPS.

As with Reverse RTSP, the integrated security system of an embodimentsupports Reverse HTTP. Reverse HTTP includes taking a TCP-based protocollike HTTP, and reversing the roles of client and server when it comes toTCP session establishment. For example, in conventional HTTP the HTTPclient is the one that establishes the TCP connection with the server(the server listens on a port for incoming connections). In ReverseHTTP, the HTTP client listens on a port for incoming connections fromthe server. Once the TCP connection is established, the HTTP clientbegins sending commands to the server over the TCP connection just as itwould in standard HTTP.

When using Reverse HTTP, the video stream source is generally on a LAN,protected by a firewall. Having a device on the LAN initiate theconnection to the HTTP client outside the firewall enables easy networktraversal.

If the camera or video stream source inside the LAN does not supportReverse HTTP, then the gateway can facilitate the Reverse HTTP method byinitiating separate TCP sessions with the video stream source device andwith the Reverse HTTP client outside the LAN, and then relay allcommunication between the two sessions. In this fashion the gateway cancompensate for a stream source device that does not support ReverseHTTP.

As described in the encryption description above, the gateway canfurther compensate for missing functionalities on the device such asencryption. If the device does not support encrypted HTTP (e.g., HTTPS),then the gateway can communicate with the device using HTTP, and thenencrypt the TCP stream(s) before relaying out of the LAN to the ReverseHTTP client.

The servers of an embodiment can compensate for HTTP clients that do notsupport Reverse HTTP. In this situation, the server accepts TCPconnections from both the HTTP client and the Reverse HTTP video streamsource (which could be a gateway acting on behalf of a stream sourcedevice that does not support Reverse HTTP). The server then relays theTCP streams from the Reverse HTTP video stream source to the HTTPclient. The server can further compensate for the encryptioncapabilities of the HTTP client; if the HTTP client does not supportencryption then the server can provide an unencrypted stream to the HTTPclient even though an encrypted stream was received from the ReverseHTTP streaming video source.

The integrated security system of an embodiment supports MJPEG asdescribed above. MJPEG is a streaming technique in which a series of JPGimages are sent as the result of an HTTP request. Because MJPEG streamsare transmitted over HTTP, HTTPS can be employed for encryption and mostMJPEG clients support the resulting encrypted stream. And as with MPEG-4over HTTP, a gateway can compensate for a stream source device that doesnot support encryption by relaying the TCP streams and encrypting theTCP stream between the gateway and the stream client. In many cases thegateway is an access point for the encrypted and private Wifi network onwhich the video stream source device is located. This means thatcommunication between the gateway and the video stream source device isencrypted at the network level, and communication between the gatewayand the video stream client is encrypted at the transport level. In thisfashion the gateway can compensate for a device that does not supportHTTPS.

The integrated system of an embodiment supports Reverse HTTP. ReverseHTTP includes taking a TCP-based protocol like HTTP, and reversal of theroles of client and server when it comes to TCP session establishmentcan be employed for MJPEG streams. For example, in standard HTTP theHTTP client is the one who establishes the TCP connection with theserver (the server listens on a port for incoming connections). InReverse HTTP, the HTTP client listens on a port for incoming connectionsfrom the server. Once the TCP connection is established, the HTTP clientbegins sending commands to the server over the TCP connection just as itwould in standard HTTP.

When using Reverse HTTP, the video stream source is generally on a LAN,protected by a firewall. Having a device on the LAN initiate theconnection to the HTTP client outside the firewall enables networktraversal.

If the camera or video stream source inside the LAN does not supportReverse HTTP, then the gateway can facilitate the Reverse HTTP method byinitiating separate TCP sessions with the video stream source device andwith the Reverse HTTP client outside the LAN, and then relay allcommunication between the two sessions. In this fashion the gateway cancompensate for a stream source device that does not support ReverseHTTP.

As described in the encryption description above, the gateway canfurther compensate for missing functionalities on the device such asencryption. If the device does not support encrypted HTTP (e.g., HTTPS),then the gateway can communicate with the device using HTTP, and thenencrypt the TCP stream(s) before relaying out of the LAN to the ReverseHTTP client.

The servers can compensate for HTTP clients that do not support ReverseHTTP. In this situation, the server accepts TCP connections from boththe HTTP client and the Reverse HTTP video stream source (which could bea gateway acting on behalf of a stream source device that does notsupport Reverse HTTP). The server then relays the TCP streams from theReverse HTTP video stream source to the HTTP client. The server canfurther compensate for the encryption capabilities of the HTTP client;if the HTTP client does not support encryption then the server canprovide an unencrypted stream to the HTTP client even though anencrypted stream was received from the Reverse HTTP streaming videosource.

The integrated security system of an embodiment considers numerousparameters in determining or selecting one of the streaming formatsdescribed above for use in transferring video streams. The parametersconsidered in selecting a streaming format include, but are not limitedto, security requirements, client capabilities, device capabilities, andnetwork/system capabilities.

The security requirements for a video stream are considered indetermining an applicable streaming format in an embodiment. Securityrequirements fall into two categories, authentication and privacy, eachof which is described below.

Authentication as a security requirement means that stream clients mustpresent credentials in order to obtain a stream. Furthermore, thispresentation of credentials should be done in a way that is secure fromnetwork snooping and replays. An example of secure authentication isBasic Authentication over HTTPS. Here a username and password arepresented over an encrypted HTTPS channel so snooping and replays areprevented. Basic Authentication alone, however, is generally notsufficient for secure authentication.

Because not all streaming clients support SSL/TLS, authenticationmethods that do not require it are desirable. Such methods includeDigest Authentication and one-time requests. A one-time request is arequest that can only be made by a client one time, and the serverprevents a reuse of the same request. One-time requests are used tocontrol access to a stream source device by stream clients that do notsupport SSL/TLS. An example here is providing video access to a mobilephone. Typical mobile phone MPEG-4 viewers do not support encryption. Inthis case, one of the MPEG-4 over RTSP methods described above can beemployed to get the video stream relayed to an server. The server canthen provide the mobile phone with a one-time request Universal ResourceLocator (URL) for the relayed video stream source (via a WirelessApplication Protocol (WAP) page). Once the stream ends, the mobile phonewould need to obtain another one-time request URL from the server (viaWAP, for example) in order to view the stream again.

Privacy as a security requirement means that the contents of the videostream must be encrypted. This is a requirement that may be impossibleto satisfy on clients that do not support video stream encryption, forexample many mobile phones. If a client supports encryption for somevideo stream format(s), then the “best” of those formats should beselected. Here “best” is determined by the stream type priorityalgorithm.

The client capabilities are considered in determining an applicablestreaming format in an embodiment. In considering client capabilities,the selection depends upon the supported video stream formats thatinclude encryption, and the supported video stream formats that do notsupport encryption.

The device capabilities are considered in determining an applicablestreaming format in an embodiment. In considering device capabilities,the selection depends upon the supported video stream formats thatinclude encryption, the supported video stream formats that do notsupport encryption, and whether the device is on an encrypted privateWifi network managed by the gateway (in which case encryption at thenetwork level is not required).

The network/system capabilities are considered in determining anapplicable streaming format in an embodiment. In consideringnetwork/system capabilities, the selection depends upon characteristicsof the network or system across which the stream must travel. Thecharacteristics considered include, for example, the following: whetherthere is a gateway and/or server on the network to facilitate some ofthe fancier video streaming types or security requirements; whether theclient is on the same LAN as the gateway, meaning that network firewalltraversal is not needed.

Streaming methods with the highest priority are peer-to-peer becausethey scale best with server resources. Universal Plug and Play (UPnP)can be used by the gateway to open ports on the video stream device'sLAN router and direct traffic through those ports to the video streamdevice. This allows a video stream client to talk directly with thevideo stream device or talk directly with the gateway which can in turnfacilitate communication with the video stream device.

Another factor in determining the best video stream format to use is thesuccess of STUN and TURN methods for establishing direct peer-to-peerUDP communication between the stream source device and the streamclient. Again, the gateway and the server can help with the setup ofthis communication.

Client bandwidth availability and processing power are other factors indetermining the best streaming methods. For example, due to itsbandwidth overhead an encrypted MJPEG stream should not be consideredfor most mobile phone data networks.

Device bandwidth availability can also be considered in choosing thebest video stream format. For example, consideration can be given towhether the upstream bandwidth capabilities of the typical residentialDSL support two or more simultaneous MJPEG streams.

Components of the integrated security system of an embodiment, whileconsidering various parameters in selecting a video streaming format totransfer video streams from streaming source devices and requestingclient devices, prioritize streaming formats according to theseparameters. The parameters considered in selecting a streaming formatinclude, as described above, security requirements, client capabilities,device capabilities, and network/system capabilities. Components of theintegrated security system of an embodiment select a video streamingformat according to the following priority, but alternative embodimentscan use other priorities.

The selected format is UPnP or peer-to-peer MPEG-4 over RTSP withencryption when both requesting client device and streaming sourcedevice support this format.

The selected format is UPnP or peer-to-peer MPEG-4 over RTSP withauthentication when the requesting client device does not supportencryption or UPnP or peer-to-peer MPEG-4 over RTSP with encryption.

The selected format is UPnP (peer-to-peer) MPEG-4 over HTTPS when bothrequesting client device and streaming source device support thisformat.

The selected format is UPnP (peer-to-peer) MPEG-4 over HTTP when therequesting client device does not support encryption or UPnP(peer-to-peer) MPEG-4 over HTTPS.

The selected format is UPnP (peer-to-peer) MPEG-4 over RTSP facilitatedby gateway or touchscreen (including or incorporating gatewaycomponents) (to provide encryption), when the requesting client devicesupports encrypted RTSP and the streaming source device supports MPEG-4over RTSP.

The selected format is UPnP (peer-to-peer) MPEG-4 over HTTPS facilitatedby gateway or touchscreen (including or incorporating gatewaycomponents) (to provide encryption) when the requesting client devicesupports MPEG-4 over HTTPS and the streaming source device supportsMPEG-4 over HTTP.

The selected format is UPnP (peer-to-peer) MJPEG over HTTPS when thenetworks and devices can handle the bandwidth and both requesting clientdevice and streaming source device support MJPEG over HTTPS.

The selected format is Reverse RTSP with STUN/TURN facilitated by theserver when the streaming source device initiates SSL/TLS TCP to server,the streaming source device supports Reverse RTSP over SSL/TLS withSTUN/TURN, and the requesting client device supports RTSP withSTUN/TURN.

The selected format is Reverse RTSP with STUN/TURN facilitated by serverand gateway or touchscreen (including or incorporating gatewaycomponents) when the gateway initiates SSL/TLS TCP to the server and tothe streaming source device, the streaming source device supports RTSP,and the requesting client device supports RTSP with STUN/TURN.

The selected format is Reverse MPEG over RTSP/HTTP facilitated by theserver when the streaming source device initiates SSL/TLS TCP to server,the streaming source device supports Reverse RTSP or HTTP over SSL/TLS,and the requesting client device supports MPEG over RTSP/HTTP.

The selected format is Reverse MPEG over RTSP/HTTP facilitated by serverand gateway or touchscreen (including or incorporating gatewaycomponents) when the gateway initiates SSL/TLS TCP to server and tostreaming source device, the streaming source device supports MPEG overRTSP or HTTP, and the requesting client device supports MPEG overRTSP/HTTP.

The selected format is UPnP (peer-to-peer) MJPEG over HTTP when thenetworks and devices can handle the bandwidth and when the requestingclient device does not support encryption and does not support MPEG-4.

The selected format is Reverse MJPEG over HTTPS facilitated by theserver when the streaming source device initiates SSL/TLS TCP to server,the streaming source device supports Reverse MJPEG over SSL/TLS, and therequesting client device supports MJPEG.

The selected format is Reverse MJPEG over HTTPS facilitated by serverand gateway or touchscreen (including or incorporating gatewaycomponents) when the gateway initiates SSL/TLS TCP to the server and tothe streaming source device, the streaming source device supports MJPEG,and the requesting client device supports MJPEG.

FIG. 14 is a flow diagram of a method of integrating an external controland management application system with an existing security system,under an embodiment. Operations begin when the system is powered on1410, involving at a minimum the power-on of the gateway device, andoptionally the power-on of the connection between the gateway device andthe remote servers. The gateway device initiates 1420 a software and RFsequence to locate the extant security system. The gateway and installerinitiate and complete 1430 a sequence to ‘learn’ the gateway into thesecurity system as a valid and authorized control device. The gatewayinitiates 1440 another software and RF sequence of instructions todiscover and learn the existence and capabilities of existing RF deviceswithin the extant security system, and store this information in thesystem. These operations under the system of an embodiment are describedin further detail below.

Unlike conventional systems that extend an existing security system, thesystem of an embodiment operates utilizing the proprietary wirelessprotocols of the security system manufacturer. In one illustrativeembodiment, the gateway is an embedded computer with an IP LAN and WANconnection and a plurality of RF transceivers and software protocolmodules capable of communicating with a plurality of security systemseach with a potentially different RF and software protocol interface.After the gateway has completed the discovery and learning 1440 ofsensors and has been integrated 1450 as a virtual control device in theextant security system, the system becomes operational. Thus, thesecurity system and associated sensors are presented 1450 as accessibledevices to a potential plurality of user interface subsystems.

The system of an embodiment integrates 1460 the functionality of theextant security system with other non-security devices including but notlimited to IP cameras, touchscreens, lighting controls, door lockingmechanisms, which may be controlled via RF, wired, or powerline-basednetworking mechanisms supported by the gateway or servers.

The system of an embodiment provides a user interface subsystem 1470enabling a user to monitor, manage, and control the system andassociated sensors and security systems. In an embodiment of the system,a user interface subsystem is an HTML/XML/Javascript/Java/AJAX/Flashpresentation of a monitoring and control application, enabling users toview the state of all sensors and controllers in the extant securitysystem from a web browser or equivalent operating on a computer, PDA,mobile phone, or other consumer device.

In another illustrative embodiment of the system described herein, auser interface subsystem is an HTML/XML/Javascript/Java/AJAXpresentation of a monitoring and control application, enabling users tocombine the monitoring and control of the extant security system andsensors with the monitoring and control of non-security devicesincluding but not limited to IP cameras, touchscreens, lightingcontrols, door locking mechanisms.

In another illustrative embodiment of the system described herein, auser interface subsystem is a mobile phone application enabling users tomonitor and control the extant security system as well as othernon-security devices.

In another illustrative embodiment of the system described herein, auser interface subsystem is an application running on a keypad ortouchscreen device enabling users to monitor and control the extantsecurity system as well as other non-security devices.

In another illustrative embodiment of the system described herein, auser interface subsystem is an application operating on a TV or set-topbox connected to a TV enabling users to monitor and control the extantsecurity system as well as other non-security devices.

FIG. 15 is a block diagram of an integrated security system 1500wirelessly interfacing to proprietary security systems, under anembodiment. A security system 1510 is coupled or connected to a Gateway1520, and from Gateway 1520 coupled or connected to a plurality ofinformation and content sources across a network 1530 including one ormore web servers 1540, system databases 1550, and applications servers1560. While in one embodiment network 1530 is the Internet, includingthe World Wide Web, those of skill in the art will appreciate thatnetwork 1530 may be any type of network, such as an intranet, anextranet, a virtual private network (VPN), a mobile network, or anon-TCP/IP based network.

Moreover, other elements of the system of an embodiment may beconventional, well-known elements that need not be explained in detailherein. For example, security system 1510 could be any type home orbusiness security system, such devices including but not limited to astandalone RF home security system or a non-RF-capable wired homesecurity system with an add-on RF interface module. In the integratedsecurity system 1500 of this example, security system 1510 includes anRF-capable wireless security panel (WSP) 1511 that acts as the mastercontroller for security system 1510. Well-known examples of such a WSPinclude the GE Security Concord, Networx, and Simon panels, theHoneywell Vista and Lynx panels, and similar panels from DSC and Napco,to name a few. A wireless module 1512 includes the RF hardware andprotocol software necessary to enable communication with and control ofa plurality of wireless devices 1513. WSP 1511 may also manage wireddevices 1514 physically connected to WSP 1511 with an RS232 or RS485 orEthernet connection or similar such wired interface.

In an implementation consistent with the systems and methods describedherein, Gateway 1520 provides the interface between security system 1510and LAN and/or WAN for purposes of remote control, monitoring, andmanagement. Gateway 1520 communicates with an external web server 1540,database 1550, and application server 1560 over network 1530 (which maycomprise WAN, LAN, or a combination thereof). In this example system,application logic, remote user interface functionality, as well as userstate and account are managed by the combination of these remoteservers. Gateway 1520 includes server connection manager 1521, asoftware interface module responsible for all server communication overnetwork 1530. Event manager 1522 implements the main event loop forGateway 1520, processing events received from device manager 1524(communicating with non-security system devices including but notlimited to IP cameras, wireless thermostats, or remote door locks).Event manager 1522 further processes events and control messages fromand to security system 1510 by utilizing WSP manager 1523.

WSP manager 1523 and device manager 1524 both rely upon wirelessprotocol manager 1526 which receives and stores the proprietary orstandards-based protocols required to support security system 1510 aswell as any other devices interfacing with gateway 1520. WSP manager1523 further utilizes the comprehensive protocols and interfacealgorithms for a plurality of security systems 1510 stored in the WSP DBclient database associated with wireless protocol manager 1526. Thesevarious components implement the software logic and protocols necessaryto communicate with and manager devices and security systems 1510.Wireless Transceiver hardware modules 1525 are then used to implementthe physical RF communications link to such devices and security systems1510. An illustrative wireless transceiver 1525 is the GE SecurityDialog circuit board, implementing a 319.5 MHz two-way RF transceivermodule. In this example, RF Link 1570 represents the 319.5 MHz RFcommunication link, enabling gateway 1520 to monitor and control WSP1511 and associated wireless and wired devices 1513 and 1514,respectively.

In one embodiment, server connection manager 1521 requests and receivesa set of wireless protocols for a specific security system 1510 (anillustrative example being that of the GE Security Concord panel andsensors) and stores them in the WSP DB portion of the wireless protocolmanager 1526. WSP manager 1523 then utilizes such protocols fromwireless protocol manager 1526 to initiate the sequence of processesdetailed in FIG. 14 and FIG. 15 for learning gateway 1520 into securitysystem 1510 as an authorized control device. Once learned in, asdescribed with reference to FIG. 15 (and above), event manager 1522processes all events and messages detected by the combination of WSPmanager 1523 and the GE Security wireless transceiver module 1525.

In another embodiment, gateway 1520 incorporates a plurality of wirelesstransceivers 1525 and associated protocols managed by wireless protocolmanager 1526. In this embodiment events and control of multipleheterogeneous devices may be coordinated with WSP 1511, wireless devices1513, and wired devices 1514. For example a wireless sensor from onemanufacturer may be utilized to control a device using a differentprotocol from a different manufacturer.

In another embodiment, gateway 1520 incorporates a wired interface tosecurity system 1510, and incorporates a plurality of wirelesstransceivers 1525 and associated protocols managed by wireless protocolmanager 1526. In this embodiment events and control of multipleheterogeneous devices may be coordinated with WSP 1511, wireless devices1513, and wired devices 1514.

Of course, while an illustrative embodiment of an architecture of thesystem of an embodiment is described in detail herein with respect toFIG. 15 , one of skill in the art will understand that modifications tothis architecture may be made without departing from the scope of thedescription presented herein. For example, the functionality describedherein may be allocated differently between client and server, oramongst different server or processor-based components. Likewise, theentire functionality of the gateway 1520 described herein could beintegrated completely within an existing security system 1510. In suchan embodiment, the architecture could be directly integrated with asecurity system 1510 in a manner consistent with the currently describedembodiments.

FIG. 16 is a flow diagram for wirelessly ‘learning’ the Gateway into anexisting security system and discovering extant sensors, under anembodiment. The learning interfaces gateway 1520 with security system1510. Gateway 1520 powers up 1610 and initiates software sequences 1620and 1625 to identify accessible WSPs 1511 and wireless devices 1513,respectively (e.g., one or more WSPs and/or devices within range ofgateway 1520). Once identified, WSP 1511 is manually or automaticallyset into ‘learn mode’ 1630, and gateway 1520 utilizes availableprotocols to add 1640 itself as an authorized control device in securitysystem 1510. Upon successful completion of this task, WSP 1511 ismanually or automatically removed from ‘learn mode’ 1650.

Gateway 1520 utilizes the appropriate protocols to mimic 1660 the firstidentified device 1514. In this operation gateway 1520 identifies itselfusing the unique or pseudo-unique identifier of the first found device1514, and sends an appropriate change of state message over RF Link1570. In the event that WSP 1511 responds to this change of statemessage, the device 1514 is then added 1670 to the system in database1550. Gateway 1520 associates 1680 any other information (such as zonename or token-based identifier) with this device 1514 in database 1550,enabling gateway 1520, user interface modules, or any application toretrieve this associated information.

In the event that WSP 1511 does not respond to the change of statemessage, the device 1514 is not added 1670 to the system in database1550, and this device 1514 is identified as not being a part of securitysystem 1510 with a flag, and is either ignored or added as anindependent device, at the discretion of the system provisioning rules.Operations hereunder repeat 1685 operations 1660, 1670, 1680 for alldevices 1514 if applicable. Once all devices 1514 have been tested inthis way, the system begins operation 1690.

In another embodiment, gateway 1520 utilizes a wired connection to WSP1511, but also incorporates a wireless transceiver 1525 to communicatedirectly with devices 1514. In this embodiment, operations under 1620above are removed, and operations under 1640 above are modified so thesystem of this embodiment utilizes wireline protocols to add itself asan authorized control device in security system 1510.

A description of an example embodiment follows in which the Gateway(FIG. 15 , element 1520) is the iHub available from iControl Networks,Palo Alto, Calif., and described in detail herein. In this example thegateway is “automatically” installed with a security system.

The automatic security system installation begins with the assignment ofan authorization key to components of the security system (e.g.,gateway, kit including the gateway, etc.). The assignment of anauthorization key is done in lieu of creating a user account. Aninstaller later places the gateway in a user's premises along with thepremises security system. The installer uses a computer to navigate to aweb portal (e.g., integrated security system web interface), logs in tothe portal, and enters the authorization key of the installed gatewayinto the web portal for authentication. Once authenticated, the gatewayautomatically discovers devices at the premises (e.g., sensors, cameras,light controls, etc.) and adds the discovered devices to the system or“network”. The installer assigns names to the devices, and testsoperation of the devices back to the server (e.g., did the door open,did the camera take a picture, etc.). The security device information isoptionally pushed or otherwise propagated to a security panel and/or tothe server network database. The installer finishes the installation,and instructs the end user on how to create an account, username, andpassword. At this time the user enters the authorization key whichvalidates the account creation (uses a valid authorization key toassociate the network with the user's account). New devices maysubsequently be added to the security network in a variety of ways(e.g., user first enters a unique ID for each device/sensor and names itin the server, after which the gateway can automatically discover andconfigure the device).

A description of another example embodiment follows in which thesecurity system (FIG. 15 , element 1510) is a Dialog system and the WSP(FIG. 15 , element 1511) is a SimonXT available from General ElectricSecurity, and the Gateway (FIG. 15 , element 1520) is the iHub availablefrom iControl Networks, Palo Alto, Calif., and described in detailherein. Descriptions of the install process for the SimonXT and iHub arealso provided below.

GE Security's Dialog network is one of the most widely deployed andtested wireless security systems in the world. The physical RF networkis based on a 319.5 MHz unlicensed spectrum, with a bandwidth supportingup to 19 Kbps communications. Typical use of this bandwidth—even inconjunction with the integrated security system—is far less than that.Devices on this network can support either one-way communication (eithera transmitter or a receiver) or two-way communication (a transceiver).Certain GE Simon, Simon XT, and Concord security control panelsincorporate a two-way transceiver as a standard component. The gatewayalso incorporates the same two-way transceiver card. The physical linklayer of the network is managed by the transceiver module hardware andfirmware, while the coded payload bitstreams are made available to theapplication layer for processing.

Sensors in the Dialog network typically use a 60-bit protocol forcommunicating with the security panel transceiver, while security systemkeypads and the gateway use the encrypted 80-bit protocol. The Dialognetwork is configured for reliability, as well as low-power usage. Manydevices are supervised, i.e. they are regularly monitored by the system‘master’ (typically a GE security panel), while still maintainingexcellent power usage characteristics. A typical door window sensor hasa battery life in excess of 5-7 years.

The gateway has two modes of operation in the Dialog network: a firstmode of operation is when the gateway is configured or operates as a‘slave’ to the GE security panel; a second mode of operation is when thegateway is configured or operates as a ‘master’ to the system in theevent a security panel is not present. In both configurations, thegateway has the ability to ‘listen’ to network traffic, enabling thegateway to continually keep track of the status of all devices in thesystem. Similarly, in both situations the gateway can address andcontrol devices that support setting adjustments (such as the GEwireless thermostat).

In the configuration in which the gateway acts as a ‘slave’ to thesecurity panel, the gateway is ‘learned into’ the system as a GEwireless keypad. In this mode of operation, the gateway emulates asecurity system keypad when managing the security panel, and can querythe security panel for status and ‘listen’ to security panel events(such as alarm events).

The gateway incorporates an RF Transceiver manufactured by GE Security,but is not so limited. This transceiver implements the Dialog protocolsand handles all network message transmissions, receptions, and timing.As such, the physical, link, and protocol layers of the communicationsbetween the gateway and any GE device in the Dialog network are totallycompliant with GE Security specifications.

At the application level, the gateway emulates the behavior of a GEwireless keypad utilizing the GE Security 80-bit encrypted protocol, andonly supported protocols and network traffic are generated by thegateway. Extensions to the Dialog RF protocol of an embodiment enablefull control and configuration of the panel, and iControl can bothautomate installation and sensor enrollment as well as directconfiguration downloads for the panel under these protocol extensions.

As described above, the gateway participates in the GE Security networkat the customer premises. Because the gateway has intelligence and atwo-way transceiver, it can ‘hear’ all of the traffic on that network.The gateway makes use of the periodic sensor updates, state changes, andsupervisory signals of the network to maintain a current state of thepremises. This data is relayed to the integrated security system server(e.g., FIG. 2 , element 104) and stored in the event repository for useby other server components. This usage of the GE Security RF network iscompletely non-invasive; there is no new data traffic created to supportthis activity.

The gateway can directly (or indirectly through the Simon XT panel)control two-way devices on the network. For example, the gateway candirect a GE Security Thermostat to change its setting to ‘Cool’ from‘Off’, as well as request an update on the current temperature of theroom. The gateway performs these functions using the existing GE Dialogprotocols, with little to no impact on the network; a gateway devicecontrol or data request takes only a few dozen bytes of data in anetwork that can support 19 Kbps.

By enrolling with the Simon XT as a wireless keypad, as describedherein, the gateway includes data or information of all alarm events, aswell as state changes relevant to the security panel. This informationis transferred to the gateway as encrypted packets in the same way thatthe information is transferred to all other wireless keypads on thenetwork.

Because of its status as an authorized keypad, the gateway can alsoinitiate the same panel commands that a keypad can initiate. Forexample, the gateway can arm or disarm the panel using the standardDialog protocol for this activity. Other than the monitoring of standardalarm events like other network keypads, the only incremental datatraffic on the network as a result of the gateway is the infrequentremote arm/disarm events that the gateway initiates, or infrequentqueries on the state of the panel.

The gateway is enrolled into the Simon XT panel as a ‘slave’ devicewhich, in an embodiment, is a wireless keypad. This enables the gatewayfor all necessary functionality for operating the Simon XT systemremotely, as well as combining the actions and information ofnon-security devices such as lighting or door locks with GE Securitydevices. The only resource taken up by the gateway in this scenario isone wireless zone (sensor ID).

The gateway of an embodiment supports three forms of sensor and panelenrollment/installation into the integrated security system, but is notlimited to this number of enrollment/installation options. Theenrollment/installation options of an embodiment include installerinstallation, kitting, and panel, each of which is described below.

Under the installer option, the installer enters the sensor IDs at timeof installation into the integrated security system web portal oriScreen. This technique is supported in all configurations andinstallations.

Kits can be pre-provisioned using integrated security systemprovisioning applications when using the kitting option. At kittingtime, multiple sensors are automatically associated with an account, andat install time there is no additional work required.

In the case where a panel is installed with sensors already enrolled(i.e. using the GE Simon XT enrollment process), the gateway has thecapability to automatically extract the sensor information from thesystem and incorporate it into the user account on the integratedsecurity system server.

The gateway and integrated security system of an embodiment uses anauto-learn process for sensor and panel enrollment in an embodiment. Thedeployment approach of an embodiment can use additional interfaces thatGE Security is adding to the Simon XT panel. With these interfaces, thegateway has the capability to remotely enroll sensors in the panelautomatically. The interfaces include, but are not limited to, thefollowing: EnrollDevice(ID, type, name, zone, group);SetDeviceParameters(ID, type, Name, zone, group),GetDeviceParameters(zone); and RemoveDevice(zone).

The integrated security system incorporates these new interfaces intothe system, providing the following install process. The install processcan include integrated security system logistics to handle kitting andpre-provisioning. Pre-kitting and logistics can include apre-provisioning kitting tool provided by integrated security systemthat enables a security system vendor or provider (“provider”) to offerpre-packaged initial ‘kits’. This is not required but is recommended forsimplifying the install process. This example assumes a ‘Basic’ kit ispreassembled and includes one (1) Simon XT, three (3) Door/windowsensors, one (1) motion sensor, one (1) gateway, one (1) keyfob, two (2)cameras, and ethernet cables. The kit also includes a sticker page withall Zones (1-24) and Names (full name list).

The provider uses the integrated security system kitting tool toassemble ‘Basic’ kit packages. The contents of different types ofstarter kits may be defined by the provider. At the distributionwarehouse, a worker uses a bar code scanner to scan each sensor and thegateway as it is packed into the box. An ID label is created that isattached to the box. The scanning process automatically associates allthe devices with one kit, and the new ID label is the unique identifierof the kit. These boxes are then sent to the provider for distributionto installer warehouses. Individual sensors, cameras, etc. are also sentto the provider installer warehouse. Each is labeled with its ownbarcode/ID.

An installation and enrollment procedure of a security system includingan gateway is described below as one example of the installationprocess.

Order and Physical Install Process

-   -   a. Once an order is generated in the iControl system, an account        is created and an install ticket is created and sent        electronically to the provider for assignment to an installer.    -   b. The assigned installer picks up his/her ticket(s) and fills        his/her truck with Basic and/or Advanced starter kits. He/she        also keeps a stock of individual sensors, cameras, iHubs, Simon        XTs, etc. Optionally, the installer can also stock homeplug        adapters for problematic installations.    -   c. The installer arrives at the address on the ticket, and pulls        out the Basic kit. The installer determines sensor locations        from a tour of the premises and discussion with the homeowner.        At this point assume the homeowner requests additional equipment        including an extra camera, two (2) additional door/window        sensors, one (1) glass break detector, and one (1) smoke        detector.    -   d. Installer mounts SimonXT in the kitchen or other location in        the home as directed by the homeowner, and routes the phone line        to Simon XT if available. GPRS and Phone numbers pre-programmed        in SimonXT to point to the provider Central Monitoring Station        (CMS).    -   e. Installer places gateway in the home in the vicinity of a        router and cable modem. Installer installs an ethernet line from        gateway to router and plugs gateway into an electrical outlet.

Associate and Enroll gateway into SimonXT

-   -   f. Installer uses either his/her own laptop plugged into router,        or homeowners computer to go to the integrated security system        web interface and log in with installer ID/pass.    -   g. Installer enters ticket number into admin interface, and        clicks ‘New Install’ button. Screen prompts installer for kit ID        (on box's barcode label).    -   h. Installer clicks ‘Add SimonXT’. Instructions prompt installer        to put Simon XT into install mode, and add gateway as a wireless        keypad. It is noted that this step is for security only and can        be automated in an embodiment.    -   i. Installer enters the installer code into the Simon XT.        Installer Learns ‘gateway’ into the panel as a wireless keypad        as a group 1 device.    -   j. Installer goes back to Web portal, and clicks the ‘Finished        Adding SimonXT’ button.

Enroll Sensors into SimonXT via iControl

-   -   k. All devices in the Basic kit are already associated with the        user's account.    -   l. For additional devices, Installer clicks ‘Add Device’ and        adds the additional camera to the user's account (by typing in        the camera ID/Serial #).    -   m. Installer clicks ‘Add Device’ and adds other sensors (two (2)        door/window sensors, one (1) glass break sensor, and one (1)        smoke sensor) to the account (e.g., by typing in IDs).    -   n. As part of Add Device, Installer assigns zone, name, and        group to the sensor. Installer puts appropriate Zone and Name        sticker on the sensor temporarily.    -   o. All sensor information for the account is pushed or otherwise        propagated to the iConnect server, and is available to propagate        to CMS automation software through the CMS application        programming interface (API).    -   p. Web interface displays ‘Installing Sensors in System . . . ’        and automatically adds all of the sensors to the Simon XT panel        through the GE RF link.    -   q. Web interface displays ‘Done Installing’→all sensors show        green.

Place and Tests Sensors in Home

-   -   r. Installer physically mounts each sensor in its desired        location, and removes the stickers.    -   s. Installer physically mounts WiFi cameras in their location        and plugs into AC power. Optional fishing of low voltage wire        through wall to remove dangling wires. Camera transformer is        still plugged into outlet but wire is now inside the wall.    -   t. Installer goes to Web interface and is prompted for automatic        camera install. Each camera is provisioned as a private,        encrypted Wifi device on the gateway secured sandbox network,        and firewall NAT traversal is initiated. Upon completion the        customer is prompted to test the security system.    -   u. Installer selects the ‘Test System’ button on the web        portal—the SimonXT is put into Test mode by the gateway over GE        RF.    -   v. Installer manually tests the operation of each sensor,        receiving an audible confirmation from SimonXT.    -   w. gateway sends test data directly to CMS over broadband link,        as well as storing the test data in the user's account for        subsequent report generation.    -   x. Installer exits test mode from the Web portal.

Installer instructs customer on use of the Simon XT, and shows customerhow to log into the iControl web and mobile portals. Customer creates ausername/password at this time.

Installer instructs customer how to change Simon XT user code from theWeb interface. Customer changes user code which is pushed to SimonXTautomatically over GE RF.

An installation and enrollment procedure of a security system includingan gateway is described below as an alternative example of theinstallation process. This installation process is for use for enrollingsensors into the SimonXT and integrated security system and iscompatible with all existing GE Simon panels.

The integrated security system supports all pre-kitting functionalitydescribed in the installation process above. However, for the purpose ofthe following example, no kitting is used.

Order and Physical Install Process

-   -   a. Once an order is generated in the iControl system, an account        is created and an install ticket is created and sent        electronically to the security system provider for assignment to        an installer.    -   b. The assigned installer picks up his/her ticket(s) and fills        his/her truck with individual sensors, cameras, iHubs, Simon        XTs, etc. Optionally, the installer can also stock homeplug        adapters for problematic installations.    -   c. The installer arrives at the address on the ticket, and        analyzes the house and talks with the homeowner to determine        sensor locations. At this point assume the homeowner requests        three (3) cameras, five (5) door/window sensors, one (1) glass        break detector, one (1) smoke detector, and one (1) keyfob.    -   d. Installer mounts SimonXT in the kitchen or other location in        the home. The installer routes a phone line to Simon XT if        available. GPRS and Phone numbers are pre-programmed in SimonXT        to point to the provider CMS.    -   e. Installer places gateway in home in the vicinity of a router        and cable modem, and installs an ethernet line from gateway to        the router, and plugs gateway into an electrical outlet.

Associate and Enroll Gateway into SimonXT

-   -   f. Installer uses either his/her own laptop plugged into router,        or homeowners computer to go to the integrated security system        web interface and log in with an installer ID/pass.    -   g. Installer enters ticket number into admin interface, and        clicks ‘New Install’ button. Screen prompts installer to add        devices.    -   h. Installer types in ID of gateway, and it is associated with        the user's account.    -   i. Installer clicks ‘Add Device’ and adds the cameras to the        user's account (by typing in the camera ID/Serial #).    -   j. Installer clicks ‘Add SimonXT’. Instructions prompt installer        to put Simon XT into install mode, and add gateway as a wireless        keypad.    -   k. Installer goes to Simon XT and enters the installer code into        the Simon XT. Learns ‘gateway’ into the panel as a wireless        keypad as group 1 type sensor.    -   l. Installer returns to Web portal, and clicks the ‘Finished        Adding SimonXT’ button.    -   m. Gateway now is alerted to all subsequent installs over the        security system RF.

Enroll Sensors into SimonXT via iControl

-   -   n. Installer clicks ‘Add Simon XT Sensors’—Displays instructions        for adding sensors to Simon XT.    -   o. Installer goes to Simon XT and uses Simon XT install process        to add each sensor, assigning zone, name, group. These        assignments are recorded for later use.    -   p. The gateway automatically detects each sensor addition and        adds the new sensor to the integrated security system.    -   q. Installer exits install mode on the Simon XT, and returns to        the Web portal.    -   r. Installer clicks ‘Done Adding Devices’.    -   s. Installer enters zone/sensor naming from recorded notes into        integrated security system to associate sensors to friendly        names.    -   t. All sensor information for the account is pushed to the        iConnect server, and is available to propagate to CMS automation        software through the CMS API.

Place and Tests Sensors in Home

-   -   u. Installer physically mounts each sensor in its desired        location.    -   v. Installer physically mounts Wifi cameras in their location        and plugs into AC power. Optional fishing of low voltage wire        through wall to remove dangling wires. Camera transformer is        still plugged into outlet but wire is now inside the wall.    -   w. Installer puts SimonXT into Test mode from the keypad.    -   x. Installer manually tests the operation of each sensor,        receiving an audible confirmation from SimonXT.    -   y. Installer exits test mode from the Simon XT keypad.    -   z. Installer returns to web interface and is prompted to        automatically set up cameras. After waiting for completion        cameras are now provisioned and operational.

Installer instructs customer on use of the Simon XT, and shows customerhow to log into the integrated security system web and mobile portals.Customer creates a username/password at this time.

Customer and Installer observe that all sensors/cameras are green.

Installer instructs customer how to change Simon XT user code from thekeypad. Customer changes user code and stores in SimonXT.

The first time the customer uses the web portal to Arm/Disarm system theweb interface prompts the customer for the user code, which is thenstored securely on the server. In the event the user code is changed onthe panel the web interface once again prompts the customer.

The panel of an embodiment can be programmed remotely. The CMS pushesnew programming to SimonXT over a telephone or GPRS link. Optionally,iControl and GE provide a broadband link or coupling to the gateway andthen a link from the gateway to the Simon XT over GE RF.

As described above, computer networks suitable for use with theembodiments described herein include local area networks (LAN), widearea networks (WAN), Internet, or other connection services and networkvariations such as the world wide web, the public internet, a privateinternet, a private computer network, a public network, a mobilenetwork, a cellular network, a value-added network, and the like.Computing devices coupled or connected to the network may be anymicroprocessor controlled device that permits access to the network,including terminal devices, such as personal computers, workstations,servers, mini computers, main-frame computers, laptop computers, mobilecomputers, palm top computers, hand held computers, mobile phones, TVset-top boxes, or combinations thereof. The computer network may includeone of more LANs, WANs, Internets, and computers. The computers mayserve as servers, clients, or a combination thereof.

The integrated security system can be a component of a single system,multiple systems, and/or geographically separate systems. The integratedsecurity system can also be a subcomponent or subsystem of a singlesystem, multiple systems, and/or geographically separate systems. Theintegrated security system can be coupled to one or more othercomponents (not shown) of a host system or a system coupled to the hostsystem.

One or more components of the integrated security system and/or acorresponding system or application to which the integrated securitysystem is coupled or connected includes and/or runs under and/or inassociation with a processing system. The processing system includes anycollection of processor-based devices or computing devices operatingtogether, or components of processing systems or devices, as is known inthe art. For example, the processing system can include one or more of aportable computer, portable communication device operating in acommunication network, and/or a network server. The portable computercan be any of a number and/or combination of devices selected from amongpersonal computers, personal digital assistants, portable computingdevices, and portable communication devices, but is not so limited. Theprocessing system can include components within a larger computersystem.

The processing system of an embodiment includes at least one processorand at least one memory device or subsystem. The processing system canalso include or be coupled to at least one database. The term“processor” as generally used herein refers to any logic processingunit, such as one or more central processing units (CPUs), digitalsignal processors (DSPs), application-specific integrated circuits(ASIC), etc. The processor and memory can be monolithically integratedonto a single chip, distributed among a number of chips or components,and/or provided by some combination of algorithms. The methods describedherein can be implemented in one or more of software algorithm(s),programs, firmware, hardware, components, circuitry, in any combination.

The components of any system that includes the integrated securitysystem can be located together or in separate locations. Communicationpaths couple the components and include any medium for communicating ortransferring files among the components. The communication paths includewireless connections, wired connections, and hybrid wireless/wiredconnections. The communication paths also include couplings orconnections to networks including local area networks (LANs),metropolitan area networks (MANs), wide area networks (WANs),proprietary networks, interoffice or backend networks, and the Internet.Furthermore, the communication paths include removable fixed mediumslike floppy disks, hard disk drives, and CD-ROM disks, as well as flashRAM, Universal Serial Bus (USB) connections, RS-232 connections,telephone lines, buses, and electronic mail messages.

Embodiments of the integrated security system described herein include asystem comprising: a gateway located at a first location; a video enginecoupled to the gateway, the video engine automatically establishing acoupling with a camera device installed at the first location, whereinthe video engine forms a segregated network with the camera device viathe coupling; and a security server located at a second locationdifferent from the first location, the security server coupled to thegateway, the security server and the video engine communicating tocontrol routing of a video stream from the camera device to a requestingclient device, the requesting client device remote to the first locationand the second location.

The gateway of an embodiment is connected to a local area network at thefirst location, and the local area network is coupled to a wide areanetwork via a router at the first location.

The gateway of an embodiment is coupled to a wide area network and iscoupled to a local area network at the first location via the connectionmanagement component and a router at the first location.

The gateway of an embodiment is coupled to the security server via theinternet.

The routing of an embodiment is Universal Plug and Play port forwarding.

The routing of an embodiment is relay server routing.

The routing of an embodiment is Simple Traversal of User DatagramProtocol (UDP) through Network Address Translators (NAT)(STUN)/Traversal Using Relay NAT (TURN) peer-to-peer routing.

The video stream of an embodiment is encrypted.

The gateway of an embodiment encrypts the video stream received from thecamera device.

The video stream of an embodiment is a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream.

The requesting client device of an embodiment initiates and establishesa Transmission Control Protocol (TCP) connection with the securityserver.

The security server of an embodiment initiates and establishes aTransmission Control Protocol (TCP) connection with the requestingclient device.

The routing of an embodiment is Simple Traversal of User DatagramProtocol (UDP) through Network Address Translators (NAT)(STUN)/Traversal Using Relay NAT (TURN) peer-to-peer routing.

The video stream of an embodiment is a Motion Picture Experts Group(MPEG)-4 (MPEG-4) over Hypertext Transfer Protocol (HTTP) video stream.

The requesting client device of an embodiment initiates and establishesa Hypertext Transfer Protocol (HTTP) Transmission Control Protocol (TCP)connection with the security server.

The security server of an embodiment initiates and establishes aHypertext Transfer Protocol (HTTP) Transmission Control Protocol (TCP)connection with the requesting client device.

The video stream of an embodiment is a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) video stream.

The requesting client device of an embodiment initiates and establishesa Hypertext Transfer Protocol (HTTP) Transmission Control Protocol (TCP)connection with the security server.

The security server of an embodiment initiates and establishes aHypertext Transfer Protocol (HTTP) Transmission Control Protocol (TCP)connection with the requesting client device.

A format of the video stream of an embodiment is automatically selectedby at least one of the gateway and the security server.

The format of an embodiment is one of Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) format, a MPEG-4over Hypertext Transfer Protocol (HTTP) format, and a Motion JointPhotographic Experts Group (JPEG) (MJPEG) format.

The format of an embodiment is selected based on a capability of therequesting client device.

The format of an embodiment is selected based on a capability of thecamera device.

The format of an embodiment is selected based on an authenticationrequirement of the requesting client device.

The format of an embodiment is selected based on a privacy requirementof the requesting client device.

The format of an embodiment is selected based on a determined capabilityof a network coupling the gateway to the requesting client device,wherein the determined capability is determined by at least one of thegateway and the security server.

The determined capability of an embodiment is relative success among aplurality of routings of the video stream.

The determined capability of an embodiment is relative success ofUniversal Plug and Play port forwarding.

The determined capability of an embodiment is relative success of SimpleTraversal of User Datagram Protocol (UDP) through Network AddressTranslators (NAT) (STUN)/Traversal Using Relay NAT (TURN) peer-to-peerrouting.

The determined capability of an embodiment is bandwidth availability ofthe requesting client device.

The determined capability of an embodiment is processing capability ofthe requesting client device.

The determined capability of an embodiment is bandwidth availability ofthe camera device.

The format of the video stream of an embodiment is automaticallyselected according to a priority.

The system of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream withencryption has a first priority.

The system of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream withencryption has a second priority.

The system of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4) Hyptertext Transfer Protocol over Secure Socket Layer(HTTPS) video stream has a third priority.

The system of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4) Hyptertext Transfer Protocol (HTTP) video stream has afourth priority.

The system of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream has afifth priority, wherein the gateway encrypts the video stream from thecamera device.

The system of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4) Hyptertext Transfer Protocol over Secure Socket Layer(HTTPS) video stream has a sixth priority, wherein the gateway encryptsthe video stream from the camera device.

The system of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) Hyptertext Transfer Protocol over Secure SocketLayer (HTTPS) video stream has a seventh priority.

The system of an embodiment, wherein a Reverse Real-Time StreamingProtocol (RTSP) video stream has an eighth priority, wherein thesecurity server initiates and establishes a Transmission ControlProtocol (TCP) connection with the requesting client device, wherein thesecurity server facilitates Simple Traversal of User Datagram Protocol(UDP) through Network Address Translators (NAT) (STUN)/Traversal UsingRelay NAT (TURN) peer-to-peer routing.

The system of an embodiment, wherein a Reverse Real-Time StreamingProtocol (RTSP) video stream has a ninth priority, wherein the securityserver initiates and establishes a Transmission Control Protocol (TCP)connection with the requesting client device, wherein one of the gatewayand the security server facilitates Simple Traversal of User DatagramProtocol (UDP) through Network Address Translators (NAT)(STUN)/Traversal Using Relay NAT (TURN) peer-to-peer routing.

The system of an embodiment, wherein a Reverse Motion Picture ExpertsGroup (MPEG)-4 (MPEG-4) over Real-Time Streaming Protocol (RTSP) videostream has a tenth priority, wherein the security server facilitatesHyptertext Transfer Protocol (HTTP) routing.

The system of an embodiment, wherein a Reverse Motion Picture ExpertsGroup (MPEG)-4 (MPEG-4) over Real-Time Streaming Protocol (RTSP) videostream has an eleventh priority, wherein one of the gateway and thesecurity server facilitates Hyptertext Transfer Protocol (HTTP) routing.

The system of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) over Hyptertext Transfer Protocol (HTTP) videostream has a twelfth priority.

The system of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) over Hyptertext Transfer Protocol over SecureSocket Layer (HTTPS) video stream has a thirteenth priority, wherein thesecurity server facilitates routing.

The system of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) over Hyptertext Transfer Protocol over SecureSocket Layer (HTTPS) video stream has a fourteenth priority, wherein oneof the gateway and the security server facilitates routing.

The requesting client device of an embodiment includes one or more of apersonal computer, a personal digital assistant, a cellular telephone,and a mobile computing device.

The gateway of an embodiment performs audio streaming between a firstdevice and a second device, wherein the first device is located behindthe gateway at the first location and the second device is locatedoutside the gateway at a remote location.

The gateway of an embodiment performs a data transfer between a firstdevice and a second device, wherein the first device is located behindthe gateway at the first location and the second device is locatedoutside the gateway at a remote location.

The data transfer of an embodiment uses Transmission Control Protocol(TCP).

The data transfer of an embodiment uses User Datagram Protocol (UDP).

The data transfer of an embodiment uses Transmission Control Protocol(TCP) and User Datagram Protocol (UDP).

The gateway of an embodiment is coupled via a wireless coupling to asecurity system installed at the first location, the security systemincluding security system components, wherein the gateway forms asecurity network that integrates communications and functions of thesecurity system components into the security network via the wirelesscoupling.

The system of an embodiment comprises an interface coupled to thesecurity network, wherein the interface allows control of the functionsof the security network by a user.

The gateway of an embodiment automatically discovers the security systemcomponents.

The gateway of an embodiment includes protocols of the security systemfrom the security server and uses the protocols to discover the securitysystem components.

The gateway of an embodiment requests and receives protocols of thesecurity system from the security server, wherein the gateway uses theprotocols received to discover the security system components.

The gateway of an embodiment automatically establishes and controls thecommunications with the security system components.

The gateway of an embodiment automatically establishes a coupling withthe security system including the security system components.

The gateway of an embodiment manages rules of interaction between thegateway and the security system components.

The gateway of an embodiment includes definitions of the security systemcomponents.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the gateway is coupledto the central monitoring station via a secondary communication linkthat is different than the primary communication link, wherein thecentral monitoring station is located at a third location different fromthe first location and the second location.

The gateway of an embodiment transmits event data of the security systemcomponents to the central monitoring station over the secondarycommunication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The secondary communication link of an embodiment includes a broadbandcoupling.

The secondary communication link of an embodiment includes a cellularcoupling.

The gateway of an embodiment transmits messages comprising event data ofthe security system components to the requesting client device over thesecondary communication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The gateway of an embodiment receives control data for control of thesecurity system components from the requesting client device via thesecondary communication link.

Embodiments of the integrated security system described herein include asystem comprising: a gateway including a video engine located at a firstlocation, the gateway coupled to a local area network (LAN) of the firstlocation, the video engine automatically establishing a coupling with acamera device installed at the first location, wherein the video engineforms a segregated network with the camera device via the coupling; anda security server located at a second location different from the firstlocation, wherein the security server is coupled to the gateway using awide area network (WAN), the security server and the video enginecommunicating to control routing of a video stream from the cameradevice to a requesting client device, the requesting client deviceremote to the first location and the second location.

Embodiments of the integrated security system described herein include asystem comprising: a gateway located at a first location, the gatewaycoupled to a local area network (LAN) of the first location; a videoengine coupled to the gateway, the video engine automaticallyestablishing a coupling with a camera device installed at the firstlocation, wherein the video engine forms a segregated network with thecamera device via the coupling; and a security server located at asecond location different from the first location, wherein the securityserver is coupled to the gateway using a wide area network (WAN), thesecurity server and the video engine communicating to control routing ofa video stream from the camera device to a requesting client device, therequesting client device remote to the first location and the secondlocation.

Embodiments of the integrated security system described herein include asystem comprising: a gateway including a video engine located at a firstlocation, the gateway coupled to a local area network (LAN) of the firstlocation, the video engine automatically establishing a coupling with acamera device installed at the first location, wherein the video engineforms a segregated network with the camera device via the coupling; asecurity server located at a second location different from the firstlocation, wherein the security server is coupled to the gateway using awide area network (WAN), the security server and the video enginecommunicating to; and an interface coupled to the gateway and thesecurity server, the interface receiving requests from a requestingclient device for a video stream from the camera device and providingthe video stream from the camera device to the requesting client device,the requesting client device remote to the first location and the secondlocation.

Embodiments of the integrated security system described herein include asystem comprising: a security network comprising a gateway coupled to asecurity system and located at a first location, the security systemincluding a plurality of security system components, the securitynetwork comprising a plurality of camera devices installed at the firstlocation and coupled to the gateway via a secure network, wherein thegateway automatically establishes a coupling with the camera devices;and a security server located at a second location different from thefirst location, the security server coupled to the gateway, the securityserver and the gateway communicating to control routing of a videostream from the camera devices to a requesting client device, therequesting client device remote to the first location and the secondlocation.

The gateway of an embodiment is connected to a local area network at thefirst location, and the local area network is coupled to a wide areanetwork via a router at the first location.

The gateway of an embodiment is coupled to a wide area network and iscoupled to a local area network at the first location via the connectionmanagement component and a router at the first location.

The gateway of an embodiment is coupled to the security server via theinternet.

The routing of an embodiment is Universal Plug and Play port forwarding.

The routing of an embodiment is relay server routing.

The routing of an embodiment is Simple Traversal of User DatagramProtocol (UDP) through Network Address Translators (NAT)(STUN)/Traversal Using Relay NAT (TURN) peer-to-peer routing.

The video stream of an embodiment is encrypted.

The gateway of an embodiment encrypts the video stream received from thecamera device.

The video stream of an embodiment is a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream.

The requesting client device of an embodiment initiates and establishesa Transmission Control Protocol (TCP) connection with the securityserver.

The security server of an embodiment initiates and establishes aTransmission Control Protocol (TCP) connection with the requestingclient device.

The routing of an embodiment is Simple Traversal of User DatagramProtocol (UDP) through Network Address Translators (NAT)(STUN)/Traversal Using Relay NAT (TURN) peer-to-peer routing.

The video stream of an embodiment is a Motion Picture Experts Group(MPEG)-4 (MPEG-4) over Hypertext Transfer Protocol (HTTP) video stream.

The requesting client device of an embodiment initiates and establishesa Hypertext Transfer Protocol (HTTP) Transmission Control Protocol (TCP)connection with the security server.

The security server of an embodiment initiates and establishes aHypertext Transfer Protocol (HTTP) Transmission Control Protocol (TCP)connection with the requesting client device.

The video stream of an embodiment is a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) video stream.

The requesting client device of an embodiment initiates and establishesa Hypertext Transfer Protocol (HTTP) Transmission Control Protocol (TCP)connection with the security server.

The security server of an embodiment initiates and establishes aHypertext Transfer Protocol (HTTP) Transmission Control Protocol (TCP)connection with the requesting client device.

A format of the video stream of an embodiment is automatically selectedby at least one of the gateway and the security server.

The format of an embodiment is one of Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) format, a MPEG-4over Hypertext Transfer Protocol (HTTP) format, and a Motion JointPhotographic Experts Group (JPEG) (MJPEG) format.

The format of an embodiment is selected based on a capability of therequesting client device.

The format of an embodiment is selected based on a capability of thecamera device.

The format of an embodiment is selected based on an authenticationrequirement of the requesting client device.

The format of an embodiment is selected based on a privacy requirementof the requesting client device.

The format of an embodiment is selected based on a determined capabilityof a network coupling the gateway to the requesting client device,wherein the determined capability is determined by at least one of thegateway and the security server.

The determined capability of an embodiment is relative success among aplurality of routings of the video stream.

The determined capability of an embodiment is relative success ofUniversal Plug and Play port forwarding.

The determined capability of an embodiment is relative success of SimpleTraversal of User Datagram Protocol (UDP) through Network AddressTranslators (NAT) (STUN)/Traversal Using Relay NAT (TURN) peer-to-peerrouting.

The determined capability of an embodiment is bandwidth availability ofthe requesting client device.

The determined capability of an embodiment is processing capability ofthe requesting client device.

The determined capability of an embodiment is bandwidth availability ofthe camera device.

The format of the video stream of an embodiment is automaticallyselected according to a priority.

The system of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream withencryption has a first priority.

The system of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream withencryption has a second priority.

The system of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4) Hyptertext Transfer Protocol over Secure Socket Layer(HTTPS) video stream has a third priority.

The system of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4) Hyptertext Transfer Protocol (HTTP) video stream has afourth priority.

The system of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream has afifth priority, wherein the gateway encrypts the video stream from thecamera device.

The system of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4) Hyptertext Transfer Protocol over Secure Socket Layer(HTTPS) video stream has a sixth priority, wherein the gateway encryptsthe video stream from the camera device.

The system of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) Hyptertext Transfer Protocol over Secure SocketLayer (HTTPS) video stream has a seventh priority.

The system of an embodiment, wherein a Reverse Real-Time StreamingProtocol (RTSP) video stream has an eighth priority, wherein thesecurity server initiates and establishes a Transmission ControlProtocol (TCP) connection with the requesting client device, wherein thesecurity server facilitates Simple Traversal of User Datagram Protocol(UDP) through Network Address Translators (NAT) (STUN)/Traversal UsingRelay NAT (TURN) peer-to-peer routing.

The system of an embodiment, wherein a Reverse Real-Time StreamingProtocol (RTSP) video stream has a ninth priority, wherein the securityserver initiates and establishes a Transmission Control Protocol (TCP)connection with the requesting client device, wherein one of the gatewayand the security server facilitates Simple Traversal of User DatagramProtocol (UDP) through Network Address Translators (NAT)(STUN)/Traversal Using Relay NAT (TURN) peer-to-peer routing.

The system of an embodiment, wherein a Reverse Motion Picture ExpertsGroup (MPEG)-4 (MPEG-4) over Real-Time Streaming Protocol (RTSP) videostream has a tenth priority, wherein the security server facilitatesHyptertext Transfer Protocol (HTTP) routing.

The system of an embodiment, wherein a Reverse Motion Picture ExpertsGroup (MPEG)-4 (MPEG-4) over Real-Time Streaming Protocol (RTSP) videostream has an eleventh priority, wherein one of the gateway and thesecurity server facilitates Hyptertext Transfer Protocol (HTTP) routing.

The system of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) over Hyptertext Transfer Protocol (HTTP) videostream has a twelfth priority.

The system of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) over Hyptertext Transfer Protocol over SecureSocket Layer (HTTPS) video stream has a thirteenth priority, wherein thesecurity server facilitates routing.

The system of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) over Hyptertext Transfer Protocol over SecureSocket Layer (HTTPS) video stream has a fourteenth priority, wherein oneof the gateway and the security server facilitates routing.

The requesting client device of an embodiment includes one or more of apersonal computer, a personal digital assistant, a cellular telephone,and a mobile computing device.

The gateway of an embodiment is coupled via a wireless coupling to thesecurity system installed at the first location, wherein the gatewayintegrates communications and functions of the security systemcomponents into the security network via the wireless coupling.

The system of an embodiment comprises an interface coupled to thesecurity network, wherein the interface allows control of the functionsof the security network by a user.

The gateway of an embodiment automatically discovers the security systemcomponents.

The gateway of an embodiment includes protocols of the security systemfrom the security server and uses the protocols to discover the securitysystem components.

The gateway of an embodiment requests and receives protocols of thesecurity system from the security server, wherein the gateway uses theprotocols received to discover the security system components.

The gateway of an embodiment automatically establishes and controls thecommunications with the security system components.

The gateway of an embodiment automatically establishes the coupling withthe security system including the security system components.

The gateway of an embodiment manages rules of interaction between thegateway and the security system components.

The gateway of an embodiment includes definitions of the security systemcomponents.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the gateway is coupledto the central monitoring station via a secondary communication linkthat is different than the primary communication link, wherein thecentral monitoring station is located at a third location different fromthe first location and the second location.

The gateway of an embodiment transmits event data of the security systemcomponents to the central monitoring station over the secondarycommunication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The secondary communication link of an embodiment includes a broadbandcoupling.

The secondary communication link of an embodiment includes a cellularcoupling.

The gateway of an embodiment transmits messages comprising event data ofthe security system components to the requesting client device over thesecondary communication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The gateway of an embodiment receives control data for control of thesecurity system components from the requesting client device via thesecondary communication link.

The security network of an embodiment comprises network devices coupledto the gateway via a wireless coupling.

The gateway of an embodiment automatically discovers the networkdevices.

The gateway of an embodiment automatically installs the network devicesin the security network.

The gateway of an embodiment automatically configures the networkdevices for operation in the security network.

The gateway of an embodiment controls communications between the networkdevices, the security system components, and the security server.

The gateway of an embodiment transmits event data of the network devicesto the requesting client device over at least one of a plurality ofcommunication links.

The gateway of an embodiment receives control data for control of thenetwork devices from the requesting client device via at least one ofthe plurality of communication links.

The event data of an embodiment comprises changes in device states ofthe network devices, data of the network devices, and data received bythe network devices.

The security server of an embodiment creates, modifies and terminatescouplings between the gateway and the network devices.

The security server of an embodiment performs creation, modification,deletion and configuration of the network devices.

The security server of an embodiment creates automations, schedules andnotification rules associated with the network devices.

The security server of an embodiment manages access to current andlogged state data for the network devices.

The security server of an embodiment manages access to current andlogged state data for couplings between the gateway and the networkdevices.

The security server of an embodiment manages communications with thenetwork devices.

The network device of an embodiment is an Internet Protocol device.

The network device of an embodiment is a camera.

The network device of an embodiment is a touchscreen.

The network device of an embodiment is a device controller that controlsan attached device.

The network device of an embodiment is a sensor.

The security server of an embodiment creates, modifies and terminatesusers corresponding to the security system.

The security server of an embodiment creates, modifies and terminatescouplings between the gateway and the security system components.

The security server of an embodiment performs creation, modification,deletion and configuration of the security system components.

The security server of an embodiment creates automations, schedules andnotification rules associated with the security system components.

The security server of an embodiment manages access to current andlogged state data for the security system components.

The security server of an embodiment manages access to current andlogged state data for couplings between the gateway and the securitysystem components.

The security server of an embodiment manages communications with thesecurity system components.

The security server of an embodiment generates and transfersnotifications to the requesting client device, the notificationscomprising event data.

The notifications of an embodiment include one or more of short messageservice messages and electronic mail messages.

The event data of an embodiment is event data of the security systemcomponents.

The security system components of an embodiment include one or more ofsensors, cameras, input/output (I/O) devices, and accessory controllers.

Embodiments of the integrated security system described herein include asystem comprising: a security network comprising a gateway coupled to asecurity system and located at a first location, the security systemincluding a plurality of security system components, the securitynetwork comprising a plurality of camera devices installed at the firstlocation and coupled to the gateway via a secure network, wherein thegateway electronically integrates communications and functions of thecamera devices with the security system components; and a securityserver located at a second location different from the first location,the security server coupled to the security network via the gateway, thesecurity server and the gateway communicating to control routing of avideo stream from the camera devices to a requesting client device, therequesting client device remote to the first location and the secondlocation.

Embodiments of the integrated security system described herein include asystem comprising: a security network comprising a gateway coupled to asecurity server, wherein the gateway is located at a first location andcoupled to a security system, the security system including securitysystem components located at the first location, wherein the securityserver is located at a second location different from the firstlocation; and a plurality of premises devices including cameras locatedat the first location and coupled to the gateway, wherein the gatewayelectronically integrates communications and functions of the pluralityof premises devices and the security system components into the securitynetwork, wherein the gateway controls routing of a video stream from thecameras to a requesting client device, the requesting client deviceremote to the first location and the second location.

Embodiments of the integrated security system described herein include asecurity network comprising: a gateway, wherein the gateway is coupledto a security system that includes a plurality of security systemcomponents that are proprietary to the security system; a plurality ofcameras coupled to the gateway, wherein the gateway forms a premisessecurity network at a first location and couples the premises securitynetwork to a local area network of the first location, wherein thegateway forms the premises security network by automaticallyestablishing a coupling with the plurality of cameras; and anapplication server located at a second location different from the firstlocation, the application server coupled to the premises securitynetwork via the gateway and a communication network, the applicationserver and the gateway controlling delivery of a video stream from theplurality of cameras to a remote client device.

Embodiments of the integrated security system described herein include adevice comprising: a gateway comprising a processor, the gateway locatedat a first location; a connection management component coupled to theprocessor, the connection management component automaticallyestablishing a coupling with a security system installed at the firstlocation, the security system including security system components,wherein the connection management component forms a security networkthat integrates communications and functions of the security systemcomponents into the security network via the coupling; and a videoengine coupled to the processor, the video engine automatically forminga segregated network including a camera device installed at the firstlocation, the video engine controlling routing of a video stream fromthe camera device to a requesting client device that is remote to thefirst location.

The gateway of an embodiment is connected to a local area network (LAN)at the first location, and the LAN is coupled to a wide area network(WAN) via a router at the first location.

The gateway of an embodiment is coupled to a security server located ata second location different from the first location, wherein thesecurity server is coupled to the WAN, the security server and the videoengine communicating to control the routing of the video stream from thecamera device to a requesting client device, the requesting clientdevice remote to the second location.

The gateway of an embodiment is coupled to a wide area network (WAN) andis coupled to a local area network (LAN) at the first location via theconnection management component and a router at the first location,wherein the security server is coupled to the WAN.

The gateway of an embodiment is coupled to a security server located ata second location different from the first location, wherein thesecurity server is coupled to the WAN, the security server and the videoengine communicating to control the routing of the video stream from thecamera device to a requesting client device, the requesting clientdevice remote to the second location.

The routing of an embodiment is Universal Plug and Play port forwarding.

The routing of an embodiment is relay server routing.

The routing of an embodiment is Simple Traversal of User DatagramProtocol (UDP) through Network Address Translators (NAT)(STUN)/Traversal Using Relay NAT (TURN) peer-to-peer routing.

The video stream of an embodiment is encrypted.

The gateway of an embodiment encrypts the video stream received from thecamera device.

The video stream of an embodiment is a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream.

The video stream of an embodiment is a reverse of the MPEG-4/RTSP videostream such that a security server initiates and establishes aTransmission Control Protocol (TCP) connection with the requestingclient device, wherein the security server is located at a secondlocation different from the first location.

The routing of an embodiment is Simple Traversal of User DatagramProtocol (UDP) through Network Address Translators (NAT)(STUN)/Traversal Using Relay NAT (TURN) peer-to-peer routing.

The video stream of an embodiment is a Motion Picture Experts Group(MPEG)-4 (MPEG-4) over Hypertext Transfer Protocol (HTTP) video stream.

The video stream of an embodiment is a reverse of the MPEG-4 over HTTPvideo stream such that a security server initiates and establishes aHTTP Transmission Control Protocol (TCP) connection with the requestingclient device, wherein the security server is located at a secondlocation different from the first location.

The video stream of an embodiment is a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) video stream.

The video stream of an embodiment is a reverse of the MJPEG video streamsuch that a security server initiates and establishes a HypertextTransfer Protocol (HTTP) Transmission Control Protocol (TCP) connectionwith the requesting client device, wherein the security server islocated at a second location different from the first location.

A format of the video stream of an embodiment is automatically selectedby at least one of a gateway and a security server, wherein the securityserver is located at a second location different from the firstlocation.

The format of an embodiment is one of Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) format, a MPEG-4over Hypertext Transfer Protocol (HTTP) format, and a Motion JointPhotographic Experts Group (JPEG) (MJPEG) format.

The format of an embodiment is selected based on a capability of therequesting client device.

The format of an embodiment is selected based on a capability of thecamera device.

The format of an embodiment is selected based on an authenticationrequirement of the requesting client device.

The format of an embodiment is selected based on a privacy requirementof the requesting client device.

The format of an embodiment is selected based on a determined capabilityof a network coupling the gateway to the requesting client device,wherein the determined capability is determined by at least one of thegateway and a security server, wherein the security server is located ata second location different from the first location.

The determined capability of an embodiment is relative success among aplurality of routings of the video stream.

The determined capability of an embodiment is relative success ofUniversal Plug and Play port forwarding.

The determined capability of an embodiment is relative success of SimpleTraversal of User Datagram Protocol (UDP) through Network AddressTranslators (NAT) (STUN)/Traversal Using Relay NAT (TURN) peer-to-peerrouting.

The determined capability of an embodiment is bandwidth availability ofthe requesting client device.

The determined capability of an embodiment is processing capability ofthe requesting client device.

The determined capability of an embodiment is bandwidth availability ofthe camera device.

The format of the video stream of an embodiment is automaticallyselected according to a priority.

The device of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream withencryption has a first priority.

The device of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream withencryption has a second priority.

The device of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4) Hyptertext Transfer Protocol over Secure Socket Layer(HTTPS) video stream has a third priority.

The device of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4) Hyptertext Transfer Protocol (HTTP) video stream has afourth priority.

The device of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream has afifth priority, wherein the gateway encrypts the video stream from thecamera device.

The device of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4) Hyptertext Transfer Protocol over Secure Socket Layer(HTTPS) video stream has a sixth priority, wherein the gateway encryptsthe video stream from the camera device.

The device of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) Hyptertext Transfer Protocol over Secure SocketLayer (HTTPS) video stream has a seventh priority.

The device of an embodiment, wherein a Reverse Real-Time StreamingProtocol (RTSP) video stream has an eighth priority, wherein a securityserver initiates and establishes a Transmission Control Protocol (TCP)connection with the requesting client device, wherein the securityserver facilitates Simple Traversal of User Datagram Protocol (UDP)through Network Address Translators (NAT) (STUN)/Traversal Using RelayNAT (TURN) peer-to-peer routing, wherein the security server is locatedat a second location different from the first location.

The device of an embodiment, wherein a Reverse Real-Time StreamingProtocol (RTSP) video stream has a ninth priority, wherein a securityserver initiates and establishes a Transmission Control Protocol (TCP)connection with the requesting client device, wherein one of the gatewayand the security server facilitates Simple Traversal of User DatagramProtocol (UDP) through Network Address Translators (NAT)(STUN)/Traversal Using Relay NAT (TURN) peer-to-peer routing, whereinthe security server is located at a second location different from thefirst location.

The device of an embodiment, wherein a Reverse Motion Picture ExpertsGroup (MPEG)-4 (MPEG-4) over Real-Time Streaming Protocol (RTSP) videostream has a tenth priority, wherein a security server facilitatesHyptertext Transfer Protocol (HTTP) routing, wherein the security serveris located at a second location different from the first location.

The device of an embodiment, wherein a Reverse Motion Picture ExpertsGroup (MPEG)-4 (MPEG-4) over Real-Time Streaming Protocol (RTSP) videostream has an eleventh priority, wherein one of the gateway and asecurity server facilitates Hyptertext Transfer Protocol (HTTP) routing,wherein the security server is located at a second location differentfrom the first location.

The device of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) over Hyptertext Transfer Protocol (HTTP) videostream has a twelfth priority.

The device of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) over Hyptertext Transfer Protocol over SecureSocket Layer (HTTPS) video stream has a thirteenth priority, wherein asecurity server facilitates routing, wherein the security server islocated at a second location different from the first location.

The device of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) over Hyptertext Transfer Protocol over SecureSocket Layer (HTTPS) video stream has a fourteenth priority, wherein oneof the gateway and a security server facilitates routing, wherein thesecurity server is located at a second location different from the firstlocation.

The requesting client device of an embodiment includes one or more of apersonal computer, a personal digital assistant, a cellular telephone,and a mobile computing device.

The gateway of an embodiment is coupled via a wireless coupling to thesecurity system.

The device of an embodiment comprises an interface coupled to thesecurity network, wherein the interface allows control of the functionsof the security network by a user.

The gateway of an embodiment automatically discovers the security systemcomponents.

The gateway of an embodiment uses protocols of the security system todiscover the security system components.

The gateway of an embodiment automatically establishes and controls thecommunications with the security system components.

The gateway of an embodiment automatically establishes a coupling withthe security system including the security system components.

The gateway of an embodiment manages rules of interaction between thegateway and the security system components.

The gateway of an embodiment includes definitions of the security systemcomponents.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the gateway is coupledto the central monitoring station via a secondary communication linkthat is different than the primary communication link, wherein thecentral monitoring station is located at a third location different fromthe first location and the second location.

The gateway of an embodiment transmits event data of the security systemcomponents to the central monitoring station over the secondarycommunication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The secondary communication link of an embodiment includes a broadbandcoupling.

The secondary communication link of an embodiment includes a GeneralPacket Radio Service (GPRS) coupling.

The gateway of an embodiment transmits messages comprising event data ofthe security system components to the requesting client device over thesecondary communication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The gateway of an embodiment receives control data for control of thesecurity system components from the requesting client device via thesecondary communication link.

Embodiments of the integrated security system described herein include adevice comprising: a gateway including a video engine and a connectionmanagement component located at a first location, the gateway coupled toa local area network (LAN) of the first location; wherein the videoengine automatically forms a device network including a plurality ofcamera devices installed at the first location by coupling with theplurality of camera devices; wherein the connection management componentautomatically forms a security network by coupling with security systemcomponents of a security system installed at the first location; whereinthe security network integrates communications and functions of thedevice network and the security system.

Embodiments of the integrated security system described herein include adevice comprising: a gateway comprising a processor, the gateway locatedat a first location; a connection management component coupled to theprocessor, the connection management component automaticallyestablishing a coupling with a security system installed at the firstlocation, the security system including security system components,wherein the connection management component forms a security networkthat integrates communications and functions of the security systemcomponents into the security network via the coupling; and a videoengine coupled to the processor, the video engine automatically forminga segregated network including a plurality of premises devices installedat the first location, the plurality of premises devices including atleast one camera device, the video engine controlling routing of a datafrom the premises devices to a requesting client device that is remoteto the first location.

Embodiments of the integrated security system described herein include asystem comprising: a gateway located at a first location; a plurality ofcamera devices installed at the first location and coupled to thegateway via a secure network, wherein the gateway establishes the securenetwork; a firewall coupled between the gateway and a wide area network(WAN); a server coupled to the gateway via the WAN, the server locatedat a second location; the gateway and the server communicating tocontrol routing of a video stream from at least one camera device of theplurality of camera devices to the client device in response to arequest for live video received from the client device, wherein therouting uses a network protocol selected from a plurality of networkprotocols in response to capabilities of the firewall, wherein theclient device is remote to the first location and the second location.

The network protocol of an embodiment is Universal Plug and Play (UPnP)port forwarding, wherein the UPnP opens a port of the firewall.

The system of an embodiment, wherein, if UPnP port forwarding fails, thegateway and the server use Simple Traversal of User Datagram Protocol(UDP) through Network Address Translators (NAT) (STUN) to bypass thefirewall and establish a peer-to-peer coupling.

The system of an embodiment, wherein, if STUN fails, the server relaysthe video stream.

The video stream of an embodiment is encrypted.

The gateway of an embodiment encrypts the video stream received from thecamera devices.

A format of the video stream of an embodiment is automatically selectedby at least one of the gateway and the server.

The format of an embodiment is one of Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) format, a MPEG-4over Hypertext Transfer Protocol (HTTP) format, and a Motion JointPhotographic Experts Group (JPEG) (MJPEG) format.

The format of an embodiment is selected based on a capability of theclient device.

The format of an embodiment is selected based on a capability of thecamera device.

The format of an embodiment is selected based on an authenticationrequirement of the client device.

The format of an embodiment is selected based on a privacy requirementof the client device.

The format of an embodiment is selected based on a determined capabilityof the WAN, wherein the determined capability is determined by at leastone of the gateway and the server.

The determined capability of an embodiment is relative success among aplurality of routings of the video stream.

The determined capability of an embodiment is relative success ofUniversal Plug and Play port forwarding.

The determined capability of an embodiment is relative success ofpeer-to-peer routing.

The determined capability of an embodiment is bandwidth availability ofthe client device.

The determined capability of an embodiment is processing capability ofthe client device.

The determined capability of an embodiment is bandwidth availability ofthe camera devices.

The format of the video stream of an embodiment is automaticallyselected according to a priority.

The client device of an embodiment includes one or more of a personalcomputer, a personal digital assistant, a cellular telephone, and amobile computing device.

The gateway of an embodiment is coupled via a wireless coupling to asecurity system installed at the first location, the security systemincluding security system components, wherein the gateway forms asecurity network that integrates communications and functions of thesecurity system components into the security network via the wirelesscoupling.

The system of an embodiment comprises an interface coupled to thesecurity network, wherein the interface allows control of the functionsof the security network via the client device.

The gateway of an embodiment automatically discovers the security systemcomponents.

The gateway of an embodiment includes protocols of the security systemfrom the server and uses the protocols to discover the security systemcomponents.

The gateway of an embodiment requests and receives protocols of thesecurity system from the server, wherein the gateway uses the protocolsreceived to discover the security system components.

The gateway of an embodiment automatically establishes and controls thecommunications with the security system components.

The gateway of an embodiment automatically establishes a coupling withthe security system including the security system components.

The gateway of an embodiment manages rules of interaction between thegateway and the security system components.

The gateway of an embodiment includes definitions of the security systemcomponents.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the gateway is coupledto the central monitoring station via a secondary communication linkthat is different than the primary communication link, wherein thecentral monitoring station is located at a third location different fromthe first location and the second location.

The gateway of an embodiment transmits event data of the security systemcomponents to the central monitoring station over the secondarycommunication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The event data of an embodiment comprises changes data and informationof the plurality of camera devices.

The secondary communication link of an embodiment includes a broadbandcoupling.

The secondary communication link of an embodiment includes a cellularcoupling.

The gateway of an embodiment transmits messages comprising event data ofthe security system components to the client device over the secondarycommunication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The gateway of an embodiment receives control data for control of thesecurity system components from the client device via the secondarycommunication link.

Embodiments of the integrated security system described herein include asystem comprising: a gateway located at a first location; a plurality ofInternet Protocol (IP) devices installed at the first location andcoupled to the gateway via a private network, wherein the privatenetwork is segregated from any other network at the first location, thegateway automatically establishing the private network, the establishingcomprising provisioning identifiers and passwords to the plurality of IPdevices; a router coupled between the gateway and a wide area network(WAN), the router providing WAN access to the gateway and the pluralityof IP devices; and a server coupled to the gateway, the server locatedat a second location different from the first location.

The gateway of an embodiment is coupled via a wireless coupling to asecurity system installed at the first location, the security systemincluding security system components, wherein the gateway forms asecurity network that integrates communications and functions of thesecurity system components into the security network via the wirelesscoupling.

The system of an embodiment comprises an interface coupled to thesecurity network, wherein the interface allows control of the functionsof the security network via a client device remote to the first locationand the second location.

The gateway of an embodiment automatically discovers the security systemcomponents.

The gateway of an embodiment includes protocols of the security systemfrom the server and uses the protocols to discover the security systemcomponents.

The gateway of an embodiment requests and receives protocols of thesecurity system from the server, wherein the gateway uses the protocolsreceived to discover the security system components.

The gateway of an embodiment automatically establishes and controls thecommunications with the security system components.

The gateway of an embodiment automatically establishes a coupling withthe security system including the security system components.

The gateway of an embodiment manages rules of interaction between thegateway and the security system components.

The gateway of an embodiment includes definitions of the security systemcomponents.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the gateway is coupledto the central monitoring station via a secondary communication linkthat is different than the primary communication link, wherein thecentral monitoring station is located at a third location different fromthe first location and the second location.

The gateway of an embodiment transmits event data of the security systemcomponents to the central monitoring station over the secondarycommunication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The event data of an embodiment comprises changes data and informationof the plurality of IP devices.

The secondary communication link of an embodiment includes a broadbandcoupling.

The secondary communication link of an embodiment includes a cellularcoupling.

The gateway of an embodiment transmits messages comprising event data ofthe security system components to a client device over the secondarycommunication link, wherein the client device is remote to the firstlocation and the second location.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The gateway of an embodiment receives control data for control of thesecurity system components from a client device via the secondarycommunication link, wherein the client device is remote to the firstlocation and the second location.

The gateway and the server of an embodiment communicate to controlrouting of a data stream from at least one IP device of the plurality ofIP devices to a client device in response to a request for the datastream received from the client device, wherein the routing uses anetwork protocol selected from a plurality of network protocols inresponse to capabilities of the firewall, wherein the client device isremote to the first location and the second location.

The network protocol of an embodiment is Universal Plug and Play (UPnP)port forwarding, wherein the UPnP opens a port of the firewall.

The system of an embodiment, wherein, if UPnP port forwarding fails, thegateway and the server use Simple Traversal of User Datagram Protocol(UDP) through Network Address Translators (NAT) (STUN) to bypass thefirewall and establish a peer-to-peer coupling.

The system of an embodiment, wherein, if STUN fails, the server relaysthe data stream.

The data stream of an embodiment is encrypted.

The gateway of an embodiment encrypts the data stream received from theIP devices.

A format of the data stream of an embodiment is automatically selectedby at least one of the gateway and the server.

The format of an embodiment is selected based on a capability of theclient device.

The format of an embodiment is selected based on a capability of the IPdevice.

The format of an embodiment is selected based on an authenticationrequirement of the client device.

The format of an embodiment is selected based on a privacy requirementof the client device.

The format of an embodiment is selected based on a determined capabilityof the WAN, wherein the determined capability is determined by at leastone of the gateway and the server.

The determined capability of an embodiment is relative success among aplurality of routings of the data stream.

The determined capability of an embodiment is relative success ofUniversal Plug and Play port forwarding.

The determined capability of an embodiment is relative success ofpeer-to-peer routing.

The determined capability of an embodiment is bandwidth availability ofthe client device.

The determined capability of an embodiment is processing capability ofthe client device.

The determined capability of an embodiment is bandwidth availability ofthe IP devices.

The format of the data stream of an embodiment is automatically selectedaccording to a priority.

Embodiments of the integrated security system described herein include asystem comprising: a gateway located at a first location and coupled toa wide area network (WAN); a plurality of Internet Protocol (IP) devicesinstalled at the first location and coupled to the gateway via a privatenetwork, wherein the private network is segregated from any othernetwork at the first location, the gateway automatically establishingthe private network, the establishing comprising provisioningidentifiers and passwords to the plurality of IP devices; a routercoupled between the gateway and a local area network (LAN) of the firstlocation, the gateway providing WAN access to the plurality of IPdevices and the LAN; and a server coupled to the gateway, the serverlocated at a second location different from the first location.

Embodiments of the integrated security system described herein include amethod comprising: coupling a gateway comprising a video engine to anetwork located at a first location; forming a device network byautomatically establishing a coupling between the video engine and acamera device installed at the first location; establishingcommunication between the gateway and a security server located at asecond location different from the first location; and controllingrouting of a video stream from the camera device to a requesting clientdevice via communications between the security server and the videoengine, the requesting client device remote to the first location andthe second location.

The gateway of an embodiment is connected to a local area network at thefirst location, and the local area network is coupled to a wide areanetwork via a router at the first location.

The gateway of an embodiment is coupled to a wide area network and iscoupled to a local area network at the first location via the connectionmanagement component and a router at the first location.

The gateway of an embodiment is coupled to the security server via theinternet.

The routing of an embodiment is Universal Plug and Play port forwarding.

The routing of an embodiment is relay server routing.

The routing of an embodiment is Simple Traversal of User DatagramProtocol (UDP) through Network Address Translators (NAT)(STUN)/Traversal Using Relay NAT (TURN) peer-to-peer routing.

The method of an embodiment comprises encrypting the video stream.

The gateway of an embodiment encrypts the video stream received from thecamera device. The video stream of an embodiment is a Motion PictureExperts Group (MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP)video stream.

The requesting client device of an embodiment initiates and establishesa Transmission Control Protocol (TCP) connection with the securityserver.

The security server of an embodiment initiates and establishes aTransmission Control Protocol (TCP) connection with the requestingclient device.

The routing of an embodiment is Simple Traversal of User DatagramProtocol (UDP) through Network Address Translators (NAT)(STUN)/Traversal Using Relay NAT (TURN) peer-to-peer routing.

The video stream of an embodiment is a Motion Picture Experts Group(MPEG)-4 (MPEG-4) over Hypertext Transfer Protocol (HTTP) video stream.

The requesting client device of an embodiment initiates and establishesa Hypertext Transfer Protocol (HTTP) Transmission Control Protocol (TCP)connection with the security server.

The security server of an embodiment initiates and establishes aHypertext Transfer Protocol (HTTP) Transmission Control Protocol (TCP)connection with the requesting client device.

The video stream of an embodiment is a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) video stream.

The requesting client device of an embodiment initiates and establishesa Hypertext Transfer Protocol (HTTP) Transmission Control Protocol (TCP)connection with the security server.

The security server of an embodiment initiates and establishes aHypertext Transfer Protocol (HTTP) Transmission Control Protocol (TCP)connection with the requesting client device.

The system of an embodiment comprises at least one of the gateway andthe security server automatically selecting a format of the videostream.

The format of an embodiment is one of Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) format, a MPEG-4over Hypertext Transfer Protocol (HTTP) format, and a Motion JointPhotographic Experts Group (JPEG) (MJPEG) format.

The format of an embodiment is selected based on a capability of therequesting client device.

The format of an embodiment is selected based on a capability of thecamera device.

The format of an embodiment is selected based on an authenticationrequirement of the requesting client device.

The format of an embodiment is selected based on a privacy requirementof the requesting client device.

The format of an embodiment is selected based on a determined capabilityof a network coupling the gateway to the requesting client device,wherein the determined capability is determined by at least one of thegateway and the security server.

The determined capability of an embodiment is relative success among aplurality of routings of the video stream.

The determined capability of an embodiment is relative success ofUniversal Plug and Play port forwarding.

The determined capability of an embodiment is relative success of SimpleTraversal of User Datagram Protocol (UDP) through Network AddressTranslators (NAT) (STUN)/Traversal Using Relay NAT (TURN) peer-to-peerrouting.

The determined capability of an embodiment is bandwidth availability ofthe requesting client device.

The determined capability of an embodiment is processing capability ofthe requesting client device.

The determined capability of an embodiment is bandwidth availability ofthe camera device.

The system of an embodiment comprises automatically selecting the formatof the video stream according to a priority.

The method of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream withencryption has a first priority.

The method of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream withencryption has a second priority.

The method of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4) Hyptertext Transfer Protocol over Secure Socket Layer(HTTPS) video stream has a third priority.

The method of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4) Hyptertext Transfer Protocol (HTTP) video stream has afourth priority.

The method of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4)/Real-Time Streaming Protocol (RTSP) video stream has afifth priority, wherein the gateway encrypts the video stream from thecamera device.

The method of an embodiment, wherein a Motion Picture Experts Group(MPEG)-4 (MPEG-4) Hyptertext Transfer Protocol over Secure Socket Layer(HTTPS) video stream has a sixth priority, wherein the gateway encryptsthe video stream from the camera device.

The method of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) Hyptertext Transfer Protocol over Secure SocketLayer (HTTPS) video stream has a seventh priority.

The method of an embodiment, wherein a Reverse Real-Time StreamingProtocol (RTSP) video stream has an eighth priority, wherein thesecurity server initiates and establishes a Transmission ControlProtocol (TCP) connection with the requesting client device, wherein thesecurity server facilitates Simple Traversal of User Datagram Protocol(UDP) through Network Address Translators (NAT) (STUN)/Traversal UsingRelay NAT (TURN) peer-to-peer routing.

The method of an embodiment, wherein a Reverse Real-Time StreamingProtocol (RTSP) video stream has a ninth priority, wherein the securityserver initiates and establishes a Transmission Control Protocol (TCP)connection with the requesting client device, wherein one of the gatewayand the security server facilitates Simple Traversal of User DatagramProtocol (UDP) through Network Address Translators (NAT)(STUN)/Traversal Using Relay NAT (TURN) peer-to-peer routing.

The method of an embodiment, wherein a Reverse Motion Picture ExpertsGroup (MPEG)-4 (MPEG-4) over Real-Time Streaming Protocol (RTSP) videostream has a tenth priority, wherein the security server facilitatesHyptertext Transfer Protocol (HTTP) routing.

The method of an embodiment, wherein a Reverse Motion Picture ExpertsGroup (MPEG)-4 (MPEG-4) over Real-Time Streaming Protocol (RTSP) videostream has an eleventh priority, wherein one of the gateway and thesecurity server facilitates Hyptertext Transfer Protocol (HTTP) routing.

The method of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) over Hyptertext Transfer Protocol (HTTP) videostream has a twelfth priority.

The method of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) over Hyptertext Transfer Protocol over SecureSocket Layer (HTTPS) video stream has a thirteenth priority, wherein thesecurity server facilitates routing.

The method of an embodiment, wherein a Motion Joint Photographic ExpertsGroup (JPEG) (MJPEG) over Hyptertext Transfer Protocol over SecureSocket Layer (HTTPS) video stream has a fourteenth priority, wherein oneof the gateway and the security server facilitates routing.

The requesting client device of an embodiment includes one or more of apersonal computer, a personal digital assistant, a cellular telephone,and a mobile computing device.

The system of an embodiment comprises coupling the gateway via awireless coupling to a security system installed at the first location,the security system including security system components, the gatewayforming a security network that integrates communications and functionsof the security system components into the security network via thewireless coupling.

The system of an embodiment comprises an interface coupled to thesecurity network, wherein the interface allows control of the functionsof the security network by a user.

The gateway of an embodiment automatically discovers the security systemcomponents.

The gateway of an embodiment includes protocols of the security systemfrom the security server and uses the protocols to discover the securitysystem components.

The gateway of an embodiment requests and receives protocols of thesecurity system from the security server, wherein the gateway uses theprotocols received to discover the security system components.

The gateway of an embodiment automatically establishes and controls thecommunications with the security system components.

The gateway of an embodiment automatically establishes a coupling withthe security system including the security system components.

The gateway of an embodiment manages rules of interaction between thegateway and the security system components.

The gateway of an embodiment includes definitions of the security systemcomponents.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the gateway is coupledto the central monitoring station via a secondary communication linkthat is different than the primary communication link, wherein thecentral monitoring station is located at a third location different fromthe first location and the second location.

The gateway of an embodiment transmits event data of the security systemcomponents to the central monitoring station over the secondarycommunication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The secondary communication link of an embodiment includes a broadbandcoupling.

The secondary communication link of an embodiment includes a GeneralPacket Radio Service (GPRS) coupling.

The gateway of an embodiment transmits messages comprising event data ofthe security system components to the requesting client device over thesecondary communication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The gateway of an embodiment receives control data for control of thesecurity system components from the requesting client device via thesecondary communication link.

Embodiments of the integrated security system described herein include amethod comprising: coupling a gateway including a video engine and aconnection management component to a local area network (LAN) located ata first location; automatically forming a device network by establishinga coupling between the video engine and a plurality of camera devicesinstalled at the first location; and automatically forming a securitynetwork by establishing a coupling between the connection managementcomponent and security system components of a security system installedat the first location, wherein the security network integratescommunications and functions of the device network and the securitysystem.

Embodiments of the integrated security system described herein include amethod comprising: coupling a gateway comprising a processor to anetwork located at a first location; forming a security network byautomatically establishing a coupling between a connection managementcomponent coupled to the processor and a security system installed atthe first location, the security system including security systemcomponents, wherein forming the security network includes integratingcommunications and functions of the security system components into thesecurity network; forming a device network by automatically establishinga coupling between a video engine coupled to the processor and a cameradevice installed at the first location; and controlling via the gatewayrouting of a video stream from the camera device to a requesting clientdevice that is remote to the first location.

Aspects of the integrated security system and corresponding systems andmethods described herein may be implemented as functionality programmedinto any of a variety of circuitry, including programmable logic devices(PLDs), such as field programmable gate arrays (FPGAs), programmablearray logic (PAL) devices, electrically programmable logic and memorydevices and standard cell-based devices, as well as application specificintegrated circuits (ASICs). Some other possibilities for implementingaspects of the integrated security system and corresponding systems andmethods include: microcontrollers with memory (such as electronicallyerasable programmable read only memory (EEPROM)), embeddedmicroprocessors, firmware, software, etc. Furthermore, aspects of theintegrated security system and corresponding systems and methods may beembodied in microprocessors having software-based circuit emulation,discrete logic (sequential and combinatorial), custom devices, fuzzy(neural) logic, quantum devices, and hybrids of any of the above devicetypes. Of course the underlying device technologies may be provided in avariety of component types, e.g., metal-oxide semiconductor field-effecttransistor (MOSFET) technologies like complementary metal-oxidesemiconductor (CMOS), bipolar technologies like emitter-coupled logic(ECL), polymer technologies (e.g., silicon-conjugated polymer andmetal-conjugated polymer-metal structures), mixed analog and digital,etc.

It should be noted that any system, method, and/or other componentsdisclosed herein may be described using computer aided design tools andexpressed (or represented), as data and/or instructions embodied invarious computer-readable media, in terms of their behavioral, registertransfer, logic component, transistor, layout geometries, and/or othercharacteristics. Computer-readable media in which such formatted dataand/or instructions may be embodied include, but are not limited to,non-volatile storage media in various forms (e.g., optical, magnetic orsemiconductor storage media) and carrier waves that may be used totransfer such formatted data and/or instructions through wireless,optical, or wired signaling media or any combination thereof. Examplesof transfers of such formatted data and/or instructions by carrier wavesinclude, but are not limited to, transfers (uploads, downloads, e-mail,etc.) over the Internet and/or other computer networks via one or moredata transfer protocols (e.g., HTTP, FTP, SMTP, etc.). When receivedwithin a computer system via one or more computer-readable media, suchdata and/or instruction-based expressions of the above describedcomponents may be processed by a processing entity (e.g., one or moreprocessors) within the computer system in conjunction with execution ofone or more other computer programs.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in a sense of “including,but not limited to.” Words using the singular or plural number alsoinclude the plural or singular number respectively. Additionally, thewords “herein,” “hereunder,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. When theword “or” is used in reference to a list of two or more items, that wordcovers all of the following interpretations of the word: any of theitems in the list, all of the items in the list and any combination ofthe items in the list.

The above description of embodiments of the integrated security systemand corresponding systems and methods is not intended to be exhaustiveor to limit the systems and methods to the precise forms disclosed.While specific embodiments of, and examples for, the integrated securitysystem and corresponding systems and methods are described herein forillustrative purposes, various equivalent modifications are possiblewithin the scope of the systems and methods, as those skilled in therelevant art will recognize. The teachings of the integrated securitysystem and corresponding systems and methods provided herein can beapplied to other systems and methods, not only for the systems andmethods described above.

The elements and acts of the various embodiments described above can becombined to provide further embodiments. These and other changes can bemade to the integrated security system and corresponding systems andmethods in light of the above detailed description.

In general, in the following claims, the terms used should not beconstrued to limit the integrated security system and correspondingsystems and methods to the specific embodiments disclosed in thespecification and the claims, but should be construed to include allsystems that operate under the claims. Accordingly, the integratedsecurity system and corresponding systems and methods is not limited bythe disclosure, but instead the scope is to be determined entirely bythe claims.

While certain aspects of the integrated security system andcorresponding systems and methods are presented below in certain claimforms, the inventors contemplate the various aspects of the integratedsecurity system and corresponding systems and methods in any number ofclaim forms. Accordingly, the inventors reserve the right to addadditional claims after filing the application to pursue such additionalclaim forms for other aspects of the integrated security system andcorresponding systems and methods.

What is claimed is:
 1. A method comprising: receiving, by a computingdevice located at a first location, a request from a user device forvideo data from a premises device located at the first location, whereinthe computing device is configured to communicate with the premisesdevice, and wherein the user device is located at a second locationdifferent from the first location; determining, by the computing device,a capability of the user device; determining, based on the capability ofthe user device, a protocol from a plurality of protocols; and causing,based on determining that the video data cannot be transmitted via thecomputing device, the video data to be transmitted from the premisesdevice to the user device via the determined protocol.
 2. The method ofclaim 1, wherein the causing the video data to be transmitted from thepremises device to the user device comprises causing the video data tobe transmitted from the premises device to the user device via a server,wherein the computing device is configured to communicate with theserver and the server is located at a third location different from thefirst location and the second location.
 3. The method of claim 2,wherein the causing the video data to be transmitted from the premisesdevice to the user device via the server is based on determining thatthe server is capable of transmitting the video data.
 4. The method ofclaim 1, wherein the causing the video data to be transmitted from thepremises device to the user device is further based on determining thatthe video data cannot be transmitted via a server, wherein the computingdevice is configured to communicate with the server and the server islocated at a third location different from the first location and thesecond location.
 5. The method of claim 1, further comprising: receivingan address of the user device, wherein the causing the video data to betransmitted from the premises device to the user device comprisescausing the video data to be transmitted from the premises device to theuser device using the address of the user device.
 6. The method of claim1, wherein the premises device comprises at least one of a camera, asensor, a security device, a touchscreen device, a security panel, or asecurity system component.
 7. The method of claim 1, wherein thecomputing device comprises at least one of a gateway, a touchscreendevice, a controller, a router, a security panel, or a set-top box.
 8. Amethod comprising: receiving, by a server and from a user device, arequest for video data from a premises device configured to communicatewith a computing device, wherein the computing device and the premisesdevice are located at a first location, wherein the server is located ata second location different from the first location, and wherein theuser device is located at a third location different from the firstlocation and the second location; determining a capability of the userdevice; determining, based on the capability of the user device, aprotocol from a plurality of protocols; and causing, based ondetermining that the video data cannot be transmitted via the computingdevice, the video data to be transmitted from the premises device to theuser device via the determined protocol.
 9. The method of claim 8,wherein the causing the video data to be transmitted from the premisesdevice to the user device comprises causing the video data to betransmitted from the premises device to the user device via the server.10. The method of claim 9, wherein the causing the video data to betransmitted from the premises device to the user device via the serveris based on determining that the server is capable of transmitting thevideo data.
 11. The method of claim 8, wherein the causing the videodata to be transmitted from the premises device to the user device isfurther based on determining that the video data cannot be transmittedvia the server.
 12. The method of claim 8, further comprising: receivingan address of the user device, wherein the causing the video data to betransmitted from the premises device to the user device comprisescausing the video data to be transmitted from the premises device to theuser device using the address of the user device.
 13. The method ofclaim 8, wherein the premises device comprises at least one of a camera,a sensor, a security device, a touchscreen device, a security panel, ora security system component.
 14. The method of claim 8, wherein thecomputing device comprises one or more of a gateway, a touchscreendevice, a controller, a router, a security panel, or a set-top box. 15.A system comprising: a premises device configured to capture video dataand located at a first location; a computing device configured tocommunicate with the premises device and located at the first location;and a server configured to communicate with the computing device andlocated at a second location different from the first location, whereinat least one of the server or the computing device is configured toreceive, from a user device, a request for the video data captured bythe premises device and determine a capability of the user device,wherein the user device is located at a third location different fromthe first location and the second location, wherein at least one of theserver or the computing device is configured to determine, based on thecapability of the user device, a protocol from a plurality of protocols,wherein at least one of the server or the computing device is configuredto cause, based on determining that the video data cannot be transmittedvia the computing device, the video data to be transmitted from thepremises device to the user device via the determined protocol.
 16. Thesystem of claim 15, wherein causing the video data to be transmittedfrom the premises device to the user device comprises causing the videodata to be transmitted from the premises device to the user device viathe server.
 17. The system of claim 16, wherein the causing the videodata to be transmitted from the premises device to the user device viathe server is based on determining that the server is capable oftransmitting the video data.
 18. The system of claim 15, wherein thecausing the video data to be transmitted from the premises device to theuser device is further based on determining that the video data cannotbe transmitted via the server.
 19. The system of claim 15, wherein atleast one of the server or the computing device is configured to receivean address of the user device, and wherein the causing the video data tobe transmitted from the premises device to the user device comprisescausing the video data to be transmitted from the premises device to theuser device using the address of the user device.
 20. The system ofclaim 15, wherein the premises device comprises at least one of acamera, a sensor, a security device, a touchscreen device, a securitypanel, or a security system component.
 21. A device comprising: one ormore processors; and memory storing instructions that, when executed bythe one or more processors, cause the device to: receive, from a userdevice, a request for video data from a premises device located at afirst location, wherein the device is located at the first location andconfigured to communicate with the premises device, and wherein the userdevice is located at a second location different from the firstlocation; determine, by the device, a capability of the user device;determine, based on the capability of the user device, a protocol from aplurality of protocols; and cause, based on determining that the videodata cannot be transmitted via the device, the video data to betransmitted from the premises device to the user device via thedetermined protocol.
 22. The device of claim 21, wherein the video datais caused to be transmitted from the premises device to the user deviceby causing the video data to be transmitted from the premises device tothe user device via a server, wherein the device is configured tocommunicate with the server and the server is located at a thirdlocation different from the first location and the second location. 23.The device of claim 22, wherein the causing the video data to betransmitted from the premises device to the user device via the serveris based on determining that the server is capable of transmitting thevideo data.
 24. The device of claim 21, wherein the video data is causedto be transmitted from the premises device to the user device furtherbased on determining that the video data cannot be transmitted via aserver, wherein the device is configured to communicate with the serverand the server is located at a third location different from the firstlocation and the second location.
 25. The device of claim 21, whereinthe instructions, when executed by the one or more processors, furthercause the device to: receive an address of the user device, wherein thevideo data is caused to be transmitted from the premises device to theuser device by causing the video data to be transmitted from thepremises device to the user device using the address of the user device.26. The device of claim 21, wherein the premises device comprises atleast one of a camera, a sensor, a security device, a touchscreendevice, a security panel, or a security system component.
 27. The deviceof claim 21, wherein the device comprises at least one of a gateway, atouchscreen device, a controller, a router, a security panel, or aset-top box.
 28. A device comprising: one or more processors; and memorystoring instructions that, when executed by the one or more processors,cause the device to: receive, from a user device, a request for videodata from a premises device configured to communicate with a computingdevice, wherein the computing device and the premises device are locatedat a first location, wherein the device is located at a second locationdifferent from the first location, and wherein the user device islocated at a third location different from the first location and thesecond location; determine a capability of the user device; determine,based on the capability of the user device, a protocol from a pluralityof protocols; and cause, based on determining that the video data cannotbe transmitted via the computing device, the video data to betransmitted from the premises device to the user device via thedetermined protocol.
 29. The device of claim 28, wherein the video datais caused to be transmitted from the premises device to the user deviceby causing the video data to be transmitted from the premises device tothe user device via the device.
 30. The device of claim 29, wherein thecausing the video data to be transmitted from the premises device to theuser device via the device is based on determining that the device iscapable of transmitting the video data.
 31. The device of claim 28,wherein the video data is caused to be transmitted from the premisesdevice to the user device further based on determining that the videodata cannot be transmitted via the device.
 32. The device of claim 28,wherein the instructions, when executed by the one or more processors,further cause the device to: receive an address of the user device,wherein the video data is caused to be transmitted from the premisesdevice to the user device by causing the video data to be transmittedfrom the premises device to the user device using the address of theuser device.
 33. The device of claim 28, wherein the premises devicecomprises at least one of a camera, a sensor, a security device, atouchscreen device, a security panel, or a security system component.34. The device of claim 28, wherein the computing device comprises oneor more of a gateway, a touchscreen device, a controller, a router, asecurity panel, or a set-top box.